On 6/1/07, Andrew Edson <[EMAIL PROTECTED]> wrote:
At the moment, I'm supposed to be writing a program that draws information from a database, processes it a bit, then stores the information elsewhere. The database I am supposed to draw from is a Postgresql 8.1.3 db, being replicated by Slony (sorry, not sure what version, think 1.1). The replication is used to create log shipping files, which are sent out to various boxes we support. All boxes are running SuSE 9.3.
Slony is relatively young software, and log shipping support is a new feature. There are a number of bugs which have been fixed in it recently (the most recent fix was committed just yesterday). You may want to upgrade to a more recent version of slony, especially if this is a production system. On a related note, you will almost certainly want to upgrade PostgreSQL to 8.1.9 (the latest release of the 8.1 series). The program I am writing is being designed for end use by the people running
the remote boxes we're replicating (log-shipping?) to. It is supposed to draw information from the main db, and I have been requested to use a db to store the modified information as well. I can create another database without any problems, but I'd prefer to use the main one if possible, so as to be able to keep only one open connection between program and any db. I was hoping I could get around this by adding a single additional table to the localized copies of the db, to hold the processed data.
Slony doesn't replicate databases. It replicates sets of tables and sequences in databases. Slony log shipping just consists of changes against the replicated tables. Since the table you're adding isn't being replicated, there's no reason to believe it will be in any way touched by the log-shipping (assuming you don't go doing clever stuff like putting triggers on replicated tables). While the main database is replicated, the new table would have to be
location specific, not touched by the log-shipping files transferred over to the remote systems. I guess my question is 'Is this possible, or will the log-shipping files clobber my new table?'. Sorry to be so long-winded; I just wasn't sure how else to define the problem.
Please don't apologize for spending time writing your problem description! Andrew
_______________________________________________ Slony1-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/slony1-general
