From: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Payal Singh <payal(at)omniti(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: ALTER ROLE SET/RESET for multiple options |
Date: | 2016-02-17 09:52:18 |
Message-ID: | CAD21AoDdduX80nmz2BtO9vxnQH7DKMfkdQ0kPo5j143CDWg-ZQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, Feb 13, 2016 at 2:45 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Fri, Feb 12, 2016 at 1:35 PM, Payal Singh <payal(at)omniti(dot)com> wrote:
>> The feature seems to work as described, but is it necessary to enclose multiple GUC settings in a parenthesis? This seems a deviation from the usual syntax of altering multiple settings separated with comma.
>
> Well, note that you can say:
>
> ALTER USER bob SET search_path = a, b, c;
>
> I'm not sure how the parentheses help exactly; it seems like there is
> an inherit ambiguity either way.
>
I thought it would be useful for user who wants to set several GUC
parameter for each user. Especially the case where changing logging
parameter for each user.
But it might not bring us fantastic usability.
Regards,
--
Masahiko Sawada
From | Date | Subject | |
---|---|---|---|
Next Message | Rushabh Lathia | 2016-02-17 10:02:46 | Re: Should PostgresFDW ImportForeignSchema should import the remote table default expression? |
Previous Message | Matteo Melli | 2016-02-17 09:39:43 | Re: [HACKERS] Packaging of postgresql-jdbc |