Received: from sectorbase2.sectorbase.com (sectorbase2.sectorbase.com [63.88.121.62] (may be forged)) by postgresql.org (8.11.3/8.11.4) with SMTP id f7VGjpf71455; Fri, 31 Aug 2001 12:45:51 -0400 (EDT) (envelope-from vmikheev@SECTORBASE.COM) Received: by sectorbase2.sectorbase.com with Internet Mail Service (5.5.2653.19) id ; Fri, 31 Aug 2001 09:45:50 -0700 Message-ID: <3705826352029646A3E91C53F7189E32016761@sectorbase2.sectorbase.com> From: "Mikheev, Vadim" To: "'Markus Wagner'" , pgsql-general@postgresql.org, pgsql-sql@postgresql.org, pgsql-hackers@postgresql.org Subject: Re: getting the oid for a new tuple in a BEFORE trigger Date: Fri, 31 Aug 2001 09:45:49 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-15" X-Archive-Number: 200108/1064 X-Sequence-Number: 14570 > we need to control database changes within BEFORE triggers. > There is no problem with triggers called by update, but there is > a problem with triggers called by insert. > > We strongly need to know the oid of a newly inserted tuple. > In this case, we use tg_newtuple of the TriggerData structure > passed to thetrigger function, and its t_data -> t_oid will > have the value '0'. > > Using BEFORE and AFTER triggers would make our lives much harder. > > Is there any way (even hack) to get the oid the newly > inserted tuple will receive? Just set t_data->t_oid = newoid() - this is what backend does in heapam.c:heap_insert(). Vadim