Dear slony folk,

I know something funny happens to the oids of some other "backend" part
of postgres when a database becomes part of a replicating system. When I
first join a subscriber to my system, after all replication has been
setup I restart the server so that all connections to postgres get
refreshed and all data re-read. I appreciate this may be overkill but
its not a problem. I started doing this when I got errors from programs
with a connection to postgres complaining because it could no longer
find table with oid XXX.

I've got to the stage where I'm adding new sets and tables to an
established cluster. After adding a new set and getting all current
subscribers to subscribe to this, will something funny happen to my new
tables that requires postgres connections to be re-established? To try
and find out if it was the initial node joining cluster or a new set
subscribe that caused the problem I did a test setup with a small db
with one table but saw no change in table oids at all.

Am I confused about what slony changes, and the need to renew postgres
connections? And if connections do need renewing is it after the initial
cluster join or every time I change the replication details, i.e. by
adding new sets?

Thanks for your help,

Vicki


This message should be regarded as confidential. If you have received this 
email in error please notify the sender and destroy it immediately.
Statements of intent shall only become binding when confirmed in hard copy 
by an authorized signatory.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://gborg.postgresql.org/pipermail/slony1-general/attachments/20060314/65aaa494/attachment.html