On Fri, 2007-03-02 at 03:32, elein wrote: > The problem seems to be with this oid: ERROR: relation with OID 14757355 > does not exist > and this SQL CONTEXT: SQL statement "SELECT last_value::int4 FROM > _platial.sl_log_status"
This error comes from cached plans which use the slony tables which change but the plan is not invalidated. I've never seen this on subscription completion, but only when I unsubscribed a set... but the resolution I guess is to clear the connection pool (I bet you have one). Or restart the master DB. Cheers, Csaba. _______________________________________________ Slony1-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/slony1-general
