| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jan Wieck <JanWieck(at)Yahoo(dot)com> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: GUC patch for Win32 |
| Date: | 2003-05-08 15:49:41 |
| Message-ID: | 20736.1052408981@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
Jan Wieck <JanWieck(at)Yahoo(dot)com> writes:
> Tom Lane wrote:
>> On second thought, that just moves the race condition upstream (to the
>> person editing postgresql.conf) ... so never mind that idea.
> I didn't actually look at that part of the code yet ... why would any
> backend read postgresql.conf?
At SIGHUP, the postmaster re-reads postgresql.conf, and each backend
must do so too --- there's no other way for pre-existing backends to
learn about changed values. The assumption is that this happens over a
short enough timespan that it's okay from the perspective of the person
editing postgresql.conf. But if newly started backends were to read
postgresql.conf when they start, that would be bad news for someone
trying to edit postgresql.conf, because there'd be no way to know when
it would happen.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Wieck | 2003-05-08 17:30:58 | Re: GUC patch for Win32 |
| Previous Message | Jan Wieck | 2003-05-08 15:40:19 | Re: GUC patch for Win32 |