Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f6BFMDa16684 for ; Wed, 11 Jul 2001 11:22:13 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id f6BFLZJ18398; Wed, 11 Jul 2001 11:21:35 -0400 (EDT) To: kristis.makris@datasoft.com, pgsql-bugs@postgresql.org Subject: Re: ERROR: deferredTriggerGetPreviousEvent: event for tuple (0, 9) not found In-reply-to: <200107110034.f6B0YX879575@hub.org> References: <200107110034.f6B0YX879575@hub.org> Comments: In-reply-to pgsql-bugs@postgresql.org message dated "Tue, 10 Jul 2001 20:34:33 -0400" Date: Wed, 11 Jul 2001 11:21:35 -0400 Message-ID: <18395.994864895@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200107/42 X-Sequence-Number: 1820 pgsql-bugs@postgresql.org writes: > ERROR: deferredTriggerGetPreviousEvent: event for tuple (0,9) not found Hmm, are you trying to create triggers on pg_shadow? It's hard to see how that message could come from an "UPDATE pg_shadow" otherwise. Triggers on system catalogs don't work very well, because they won't be invoked as a side effect of system-initiated operations. In this situation, it appears that the trigger code sees that the pg_shadow row was inserted in the current transaction, so it tries to look up the row in the list of pending trigger events --- and doesn't find an entry, because CREATE USER didn't invoke the trigger code. In a perfect world we'd support user-defined triggers on the system catalogs, but given the potential circularity problems, I doubt it's going to happen real soon. I'd suggest finding another approach. regards, tom lane