Re: pgsql/src/backend/utils/adt (ri_triggers.c) - Mailing list pgsql-committers

From Tom Lane
Subject Re: pgsql/src/backend/utils/adt (ri_triggers.c)
Date
Msg-id 22197.969944720@sss.pgh.pa.us
Whole thread Raw
In response to Re: pgsql/src/backend/utils/adt (ri_triggers.c)  (Hiroshi Inoue <Inoue@tpf.co.jp>)
Responses Re: pgsql/src/backend/utils/adt (ri_triggers.c)  (520083510237-0001@t-online.de (Peter Eisentraut))
List pgsql-committers
Hiroshi Inoue <Inoue@tpf.co.jp> writes:
>> When the RI triggers lock the PK table, temporarily switch the current user
>> id to the owner of the PK table, to avoid permission problems.

> Are there any changes for Stephan's question ?

> Stephan Szabo wrote:
>> As a question, since I don't have a source tree available here at work,
>> will there be an issue if an elog occurs between the various two user id
>> sets?  Just wondering, because most of those statements are do some
>> SPI thing or elog.

It'll certainly be necessary for xact abort to restore the original
user ID setting.  Peter, did you do that already?

            regards, tom lane

pgsql-committers by date:

Previous
From: Hiroshi Inoue
Date:
Subject: Re: pgsql/src/backend/utils/adt (ri_triggers.c)
Next
From: Tatsuo Ishii
Date:
Subject: pgsql/src/interfaces/ecpg/preproc (pgc.l)