From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Mikheev, Vadim <vmikheev@SECTORBASE.COM>
Cc: 'Markus Wagner' <wagner@imsd.uni-mainz.de>
Cc: pgsql-general@postgresql.org
Cc: pgsql-sql@postgresql.org
Cc: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] getting the oid for a new tuple in a BEFORE
Date: Tue, 4 Sep 2001 11:33:30 -0400 (EDT)
Message-ID: <200109041533.f84FXUc09905@candle.pha.pa.us> (raw)
In-Reply-To: <3705826352029646A3E91C53F7189E32016761@sectorbase2.sectorbase.com>
> > 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().
Does that work? Doesn't that get overwritten when the actual INSERT
happens?
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
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: pgman@candle.pha.pa.us, vmikheev@SECTORBASE.COM, wagner@imsd.uni-mainz.de, pgsql-general@postgresql.org, pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] getting the oid for a new tuple in a BEFORE
In-Reply-To: <200109041533.f84FXUc09905@candle.pha.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