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

Alvaro Herrera <alvherre@2ndquadrant.com>

From: Alvaro Herrera <alvherre@2ndquadrant.com>

To: Amit Kapila <amit.kapila@huawei.com>

Cc: 'Robert Haas' <robertmhaas@gmail.com>, 'Josh Berkus' <josh@agliodbs.com>, 'Tom Lane' <tgl@sss.pgh.pa.us>, 'Magnus Hagander' <magnus@hagander.net>, 'Christopher Browne' <cbbrowne@gmail.com>, 'PostgreSQL-development' <pgsql-hackers@postgresql.org>

Date: 2012-11-08T15:18:07Z

Lists: pgsql-hackers

Amit Kapila escribió:
> On Thursday, November 08, 2012 8:07 PM Alvaro Herrera wrote:

> >The other way to
> > define this would be to have a lock that you grab and keep until end of
> > transaction, and the .auto.lock file is deleted if the transaction is
> > aborted; so have the .auto.lock -> .auto rename only happen at
> > transaction commit.
> 
> Is this behavior sane for Transaction block, as in transaction block some
> other backend might need to wait
> for little longer, if both issued a command to change config parameter?

IMO yes, it's sane to make the second backend wait until the first one
commits.

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services