Any potential race condition danger from repeated config entries?

From: Erik Jones <ejones(at)engineyard(dot)com>
To: pgsql-admin(at)postgresql(dot)org
Subject: Any potential race condition danger from repeated config entries?
Date: 2014-01-14 19:39:29
Message-ID: 8D1F2E9D-2476-4BC4-86D3-A5500970D5ED@engineyard.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-admin

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 in 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 PST,,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 PST,,0,LOG,00000,"parameter ""checkpoint_segments"" changed to ""100""",,,,,,,,,""

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

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Rosser Schwarz 2014-01-14 19:47:27 Re: changing pb_hba.conf file with pgadmin3
Previous Message Korry Douglas 2014-01-14 19:35:18 Re: changing pb_hba.conf file with pgadmin3