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

BUG #5206: wal_sync_method in stock postgresql.conf may be wrong

From: "Alvaro Herrera" <alvherre(at)postgresql(dot)org>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #5206: wal_sync_method in stock postgresql.conf may be wrong
Date: 2009-11-20 23:56:59
Message-ID: 200911202356.nAKNuxJB044989@wwwmaster.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-hackers
The following bug has been logged online:

Bug reference:      5206
Logged by:          Alvaro Herrera
Email address:      alvherre(at)postgresql(dot)org
PostgreSQL version: any
Operating system:   any
Description:        wal_sync_method in stock postgresql.conf may be wrong
Details: 

Jaime Casanova just made me note that though most commented variables in
postgresql.conf list the value that they have because of being the default,
this is not the case with wal_sync_method -- it instead says "fsync" and
then explains in a comment that the real value is something else.

Now I understand why this is (it's because of the fact that the default
value is platform-dependent), but it still is a bit unfortunate and it would
be better to avoid it.

I have two suggestions to fix this:

1. avoid displaying any value at all as if it were the true default (this
would perhaps make the line invalid were the user to uncomment it)

2. change initdb so that it modifies that line too (along with
shared_buffers etc) to put the actual default value in there, but without
uncommenting it.

I also have one non-suggestion:

3. do nothing

Thoughts?

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2009-11-21 00:02:11
Subject: Re: ecpg & 8.3 -> 8.4 migration
Previous:From: Tom LaneDate: 2009-11-20 23:47:35
Subject: Re: DEFAULT of domain ignored in plpgsql (8.4.1)

pgsql-bugs by date

Next:From: Tom LaneDate: 2009-11-21 06:02:43
Subject: Re: BUG #5201: insert select gives bogus error message
Previous:From: Alain BaeckerootDate: 2009-11-20 23:44:55
Subject: BUG #5205: Cannot ADD CONSTRAINT ... FOREIGN KEY...

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