| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "David Parker" <dparker(at)tazznetworks(dot)com> |
| Cc: | "postgres general" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: another failover testing question |
| Date: | 2005-05-26 22:00:33 |
| Message-ID: | 8879.1117144833@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"David Parker" <dparker(at)tazznetworks(dot)com> writes:
> Sorry, neglected the version yet again: 7.4.5. What happens is that we
> have active connections accessing tables that are being replicated by
> slony. Then somebody does an uninstall of slony, which removes the slony
> trigger from those tables. Then we start getting the OID error.
> If this should indeed not be an issue in 7.4.5, I will try to come up
> with a test case independent of a slony install.
It should not be ... at least, assuming that Slony is using the standard
DROP TRIGGER operation, rather than playing directly with the system
catalogs ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Devrim GUNDUZ | 2005-05-26 23:08:00 | libpq.so.3 problem, PostgreSQL >= 8.0.2 and RPM installations |
| Previous Message | Tom Lane | 2005-05-26 21:50:29 | Re: Locking rows |