"David Parker" <dparker@tazznetworks.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