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

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

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Amit Kapila <amit(dot)kapila(at)huawei(dot)com>
Cc: 'Robert Haas' <robertmhaas(at)gmail(dot)com>,'Josh Berkus' <josh(at)agliodbs(dot)com>, 'Tom Lane' <tgl(at)sss(dot)pgh(dot)pa(dot)us>,'Magnus Hagander' <magnus(at)hagander(dot)net>,'Christopher Browne' <cbbrowne(at)gmail(dot)com>,'PostgreSQL-development' <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Proposal for Allow postgresql.conf values to be changed via SQL
Date: 2012-11-08 14:36:32
Message-ID: 20121108143632.GA7225@alvh.no-ip.org (view raw or flat)
Thread:
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


In response to

Responses

pgsql-hackers by date

Next:From: Dean RasheedDate: 2012-11-08 14:38:46
Subject: Re: Proof of concept: auto updatable views [Review of Patch]
Previous:From: Amit KapilaDate: 2012-11-08 14:26:27
Subject: Re: Proposal for Allow postgresql.conf values to be changed via SQL

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