Re: Proposal for Allow postgresql.conf values to be changed via SQL - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Proposal for Allow postgresql.conf values to be changed via SQL
Date
Msg-id 20121108143632.GA7225@alvh.no-ip.org
Whole thread Raw
In response to Re: Proposal for Allow postgresql.conf values to be changed via SQL  (Amit Kapila <amit.kapila@huawei.com>)
Responses Re: Proposal for Allow postgresql.conf values to be changed via SQL
List 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



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Proposal for Allow postgresql.conf values to be changed via SQL
Next
From: Dean Rasheed
Date:
Subject: Re: Proof of concept: auto updatable views [Review of Patch]