Postgres Pro
Downloads
Home   >   mailing lists

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

From Josh Berkus
Subject Re: Proposal for Allow postgresql.conf values to be changed via SQL
Date
Msg-id 50904CB1.6010003@agliodbs.com
Whole thread Raw
In response to Re: Proposal for Allow postgresql.conf values to be changed via SQL  (Christopher Browne <cbbrowne@gmail.com>)
Responses Re: Proposal for Allow postgresql.conf values to be changed via SQL  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Proposal for Allow postgresql.conf values to be changed via SQL  (Amit Kapila <amit.kapila@huawei.com>)
List pgsql-hackers
Tree view 
> I should think that doing this requires heading back towards there
> being a single unique configuration stream, and over the course of
> several versions, deprecating the INCLUDE directive.

Oh, maybe I should take a closer look at Amit's proposal then.  I
thought we planned to make use of the INCLUDE facility for SET
PERSISTENT, including supporting include-if-exists.  Possibly what he's
proposing and what I thought our last consensus were are highly divergent.

-- 
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com

pgsql-hackers by date:

Previous
From: Christopher Browne
Date:
Subject: Re: Proposal for Allow postgresql.conf values to be changed via SQL
Next
From: Tom Lane
Date:
Subject: Limiting the number of parameterized indexpaths created