Re: ALTER ROLE SET/RESET for multiple options

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Payal Singh <payal(at)omniti(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ALTER ROLE SET/RESET for multiple options
Date: 2016-02-13 05:45:23
Message-ID: CA+TgmoZTJfVSei0484-+4m4Wx=kBh4WqPLoCBHmAoDRyKJyj6A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2016-02-13 05:50:27 Re: [COMMITTERS] pgsql: Code cleanup in the wake of recent LWLock refactoring.
Previous Message Robert Haas 2016-02-13 05:32:14 Re: [COMMITTERS] pgsql: Code cleanup in the wake of recent LWLock refactoring.