pg.ddx.io pgsql-admin@postgresql.org mailing list archivehelp / color / mirror / Atom feed
Any potential race condition danger from repeated config entries? 2+ messages / 2 participants [nested] [flat]
* Any potential race condition danger from repeated config entries? @ 2014-01-14 19:39 Erik Jones <ejones@engineyard.com> 2014-01-14 23:16 ` Re: Any potential race condition danger from repeated config entries? Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 1 reply; 2+ messages in thread From: Erik Jones @ 2014-01-14 19:39 UTC (permalink / raw) To: 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? -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin ^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: Any potential race condition danger from repeated config entries? 2014-01-14 19:39 Any potential race condition danger from repeated config entries? Erik Jones <ejones@engineyard.com> @ 2014-01-14 23:16 ` Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 2+ messages in thread From: Tom Lane @ 2014-01-14 23:16 UTC (permalink / raw) To: Erik Jones <ejones@engineyard.com>; +Cc: pgsql-admin Erik Jones <ejones@engineyard.com> writes: > 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? No. Any one process is going to read the whole config file(s) before it does anything with the new values, so the only actual effect of the earlier setting is the excess bleating in the postmaster log. regards, tom lane -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin ^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2014-01-14 23:16 UTC | newest] Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2014-01-14 19:39 Any potential race condition danger from repeated config entries? Erik Jones <ejones@engineyard.com> 2014-01-14 23:16 ` Tom Lane <tgl@sss.pgh.pa.us>
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox