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 20:29:44 |
Message-ID: | 8279.1117139384@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:
> Something that we end up doing sometimes in our failover testing is
> removing slony replication from an "active" (data provider) server.
> Because this involves removing triggers from tables, we end up with
> currently connected clients getting a bunch of "OID 123 not found"
> errors, where the OID is that of the recently removed trigger.
> Is there any way short of cycling all client connections to have the
> server processes clean that information out of their cache when an
> object disappears like this from the database?
AFAICS, there already *is* adequate interlocking for this. What PG
version are you testing, and can you provide a self-contained test case?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Jaime Casanova | 2005-05-26 20:34:34 | Re: Trigger and arguments question |
Previous Message | Hervé Inisan | 2005-05-26 19:52:39 | Trigger and arguments question |