From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Pavel Golub <pavel(at)microolap(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: AlterUserStmt anmd RoleSpec rules in grammar.y |
Date: | 2017-08-01 00:42:43 |
Message-ID: | 00ed6ee3-9af5-363d-cafd-be8d5b50a698@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 7/26/17 11:29, Tom Lane wrote:
> You'll notice that that statement fails in the regression tests:
>
> ALTER USER ALL SET application_name to 'SLAP';
> ERROR: syntax error at or near "ALL"
>
> The one that works is
>
> ALTER ROLE ALL SET application_name to 'SLAP';
>
> and the reason is that AlterRoleSetStmt has a separate production
> for ALL, but AlterUserSetStmt doesn't. This seems a tad bizarre
> though. Peter, you added that production (in commit 9475db3a4);
> is this difference intentional or just an oversight? If it's
> intentional, what's the reasoning?
That looks like a bug to me. ALTER USER also does not support the IN
DATABASE clause, so the code deviation might have started there already.
I propose the attached patch to clean this up.
For backpatching, I could develop some less invasive versions.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Attachment | Content-Type | Size |
---|---|---|
0001-Further-unify-ROLE-and-USER-command-grammar-rules.patch | text/plain | 9.4 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2017-08-01 00:54:28 | Re: PL_stashcache, or, what's our minimum Perl version? |
Previous Message | Amit Langote | 2017-08-01 00:42:13 | Re: BUG #14759: insert into foreign data partitions fail |