pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: kristis.makris@datasoft.com
To: pgsql-bugs@postgresql.org
Subject: Re: ERROR: deferredTriggerGetPreviousEvent: event for tuple (0, 9) not found
Date: Wed, 11 Jul 2001 11:21:35 -0400
Message-ID: <18395.994864895@sss.pgh.pa.us> (raw)
In-Reply-To: <200107110034.f6B0YX879575@hub.org>
References: <200107110034.f6B0YX879575@hub.org>

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



view thread (9+ messages)  latest in thread

Message-ID: <18395.994864895@sss.pgh.pa.us>
Permalink:  ../18395.994864895@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/18395.994864895@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: tgl@sss.pgh.pa.us, kristis.makris@datasoft.com, pgsql-bugs@postgresql.org
  Subject: Re: ERROR: deferredTriggerGetPreviousEvent: event for tuple (0, 9) not found
  In-Reply-To: <18395.994864895@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox