Horton
Menu

Re: User-Id Tracking when Portal was started

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Kohei KaiGai <kaigai@kaigai.gr.jp>
Cc: Robert Haas <robertmhaas@gmail.com>, PgHacker <pgsql-hackers@postgresql.org>, Florian Pflug <fgp@phlo.org>
Date: 2012-07-03T16:08:47Z
Lists: pgsql-hackers 
Kohei KaiGai <kaigai@kaigai.gr.jp> writes:
> 2012/7/3 Tom Lane <tgl@sss.pgh.pa.us>:
>> Um... what should happen if there was a SET SESSION AUTHORIZATION
>> to the portal's userId?  This test will think nothing happened.

> In my test, all the jobs by SET SESSION AUTHORIZATION was cleaned-up...
> It makes nothing happen from viewpoint of users.

My point is that it seems like a bug that the secContext gets restored
in one case and not the other, depending on which user ID was specified
in SET SESSION AUTHORIZATION.

			regards, tom lane