| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, PgHacker <pgsql-hackers(at)postgresql(dot)org>, Florian Pflug <fgp(at)phlo(dot)org> |
| Subject: | Re: User-Id Tracking when Portal was started |
| Date: | 2012-07-03 16:08:47 |
| Message-ID: | 8813.1341331727@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp> writes:
> 2012/7/3 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2012-07-03 16:09:59 | Re: Event Triggers reduced, v1 |
| Previous Message | Tom Lane | 2012-07-03 16:02:21 | Re: Posix Shared Mem patch |