Robert Haas escribió: > On Mon, Oct 26, 2009 at 12:18 AM, Greg Smith <gsm...@gregsmith.com> wrote:
> > It actually makes it completely trivial to implement. SET PERSISTENT can > > now write all the changes out to a new file in the include directory. Just > > ship the database with a persistent.conf in there that looks like this: > > This only sorta works. If the changes are written out to a file that > is processed after postgresql.conf (or some other file that contains > values for those variables), then someone who edits postgresql.conf > (or some other file) by hand will think they have changed a setting > when they really haven't. Maybe SET PERSISTENT needs to go back to postgresql.conf, add an automatic comment "# overridden in persistent.conf" and put a comment marker in front of the original line. That way the user is led to the actual authoritative source. > On the flip side, there could also be still > other files that are processed afterwards, in which case SET > PERSISTENT would appear to work but not actually do anything. Fortunately we now have an easy way to find out which file is each setting's value coming from. -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
