Skip site navigation (1) Skip section navigation (2)

Re: Proposal for Allow postgresql.conf values to be changed via SQL

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila(at)huawei(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Proposal for Allow postgresql.conf values to be changed via SQL
Date: 2012-12-03 15:41:21
Message-ID: 50BCC821.1090208@dunslane.net (view raw or flat)
Thread:
Lists: pgsql-hackers
On 12/03/2012 10:32 AM, Tom Lane wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> On Mon, Dec 3, 2012 at 6:38 AM, Amit Kapila <amit(dot)kapila(at)huawei(dot)com> wrote:
>>> opt_persistent: PERSISTENT                                { $$ = TRUE; }
>>> | /*EMPTY*/                %prec Op        { $$ = FALSE; }
>>> ;
>>>
>>> I am not sure if there are any problems with above change.
>> We usually try to avoid operator precedence declarations.  They
>> sometimes have unforeseen consequences.
> Yes.  This is not an improvement over factoring out opt_persistent as
> I recommended previously.


This is by no means the first time this has come up. See 
<http://wiki.postgresql.org/wiki/Fixing_shift/reduce_conflicts_in_Bison>

cheers

andrew



In response to

pgsql-hackers by date

Next:From: Simon RiggsDate: 2012-12-03 15:41:47
Subject: Re: [v9.3] Row-Level Security
Previous:From: Kohei KaiGaiDate: 2012-12-03 15:36:12
Subject: Re: [v9.3] Row-Level Security

Privacy Policy | About PostgreSQL
Copyright © 1996-2013 The PostgreSQL Global Development Group