From: Erik Jones <ejones@engineyard.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Any potential race condition danger from repeated config entries?
Message-Id: <8D1F2E9D-2476-4BC4-86D3-A5500970D5ED@engineyard.com>
Date: Tue, 14 Jan 2014 11:39:29 -0800
To: pgsql-admin@postgresql.org
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

For example, checkpoint_segments set to 10 in the main postgresql.conf and =
then set to 100 in an file included at the end of the main config results i=
n log messages like the following when a reload is issued:

2014-01-14 11:10:22.597 PST,,,22347,,52b8a115.574b,6,,2013-12-23 12:46:13 P=
ST,,0,LOG,00000,"parameter ""checkpoint_segments"" changed to ""10""",,,,,,=
,,,""
2014-01-14 11:10:22.597 PST,,,22347,,52b8a115.574b,7,,2013-12-23 12:46:13 P=
ST,,0,LOG,00000,"parameter ""checkpoint_segments"" changed to ""100""",,,,,=
,,,,""

At that point the server is running with a value of 100 for checkpoint segm=
ents.  Another reload results in the same two messages.  Is there any dange=
r from it being dropped to 10 and immediately set back to 100?

--=20
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin