Re: SESSION SESSION - bug or intentional?
| От | David G. Johnston |
|---|---|
| Тема | Re: SESSION SESSION - bug or intentional? |
| Дата | |
| Msg-id | CAKFQuwby6UOxRayoKELxQi_vzDhtqf2YZge-0=ufa1oJxs0KPg@mail.gmail.com обсуждение исходный текст |
| Ответ на | SESSION SESSION - bug or intentional? (Joe Conway <mail@joeconway.com>) |
| Ответы |
Re: SESSION SESSION - bug or intentional?
|
| Список | pgsql-hackers |
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_namewhich 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.
В списке pgsql-hackers по дате отправления: