Horton
Menu

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

Alvaro Herrera <alvherre@2ndquadrant.com>

View thread
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-08T14:36:32Z
Lists: pgsql-hackers 
Amit Kapila escribió:

> 3. Two backends trying to write to .auto file 
>        we can use ".auto.lock" as the the lock by trying to create it in
> exclusive mode as the first step 
>        of the command. If it already exists then backend needs to wait.

So changing .auto settings would be nontransactional?  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.

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