From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Joe Conway <mail(at)joeconway(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: SESSION SESSION - bug or intentional? |
Date: | 2015-09-30 19:10:19 |
Message-ID: | CAKFQuwby6UOxRayoKELxQi_vzDhtqf2YZge-0=ufa1oJxs0KPg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Sep 30, 2015 at 2:52 PM, Joe Conway <mail(at)joeconway(dot)com> wrote:
> I was looking at something in gram.y when I noticed that the following
> production works:
>
>
> SET SESSION SESSION CHARACTERISTICS AS TRANSACTION READ ONLY;
>
>
> "SESSION SESSION" seems fairly odd -- is it intentional?
>
Scanning the SET and SET TRANSACTION it doesn't appear to be something
they are documented as allowing.
However, SET SESSION AUTHORIZATION is defined as thus:
SET [ SESSION | LOCAL ] SESSION AUTHORIZATION user_name
which implies that we don't take pains to avoid it. Since:
"The SESSION and LOCAL modifiers are a PostgreSQL extension, as is the
RESET syntax."
The standard doesn't have any undue influence on our particular decision.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Paul Ramsey | 2015-09-30 19:33:39 | Re: [PATCH] postgres_fdw extension support |
Previous Message | Joe Conway | 2015-09-30 18:52:28 | SESSION SESSION - bug or intentional? |