Re: GUC patch for Win32

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: GUC patch for Win32
Date: 2003-05-02 04:01:49
Message-ID: 200305020401.h4241nx16582@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches


The other nice thing is that it only creates the file on startup and on
sighup, so it obeys the normal Unix behavior.

---------------------------------------------------------------------------

Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > The patch basically writes all modified GUC variables to a binary file
> > that can be read in by newly created exec'ed backends.
>
> Where exactly is the interlock to ensure that the new backend will end up
> with the correct settings if someone is changing the values at about
> the time of the fork?
>
> The relcache code has this problem solved, but I'm unconvinced that GUC
> does.
>
> regards, tom lane
>

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2003-05-02 04:14:25 Re: GUC patch for Win32
Previous Message Bruce Momjian 2003-05-02 03:58:18 Re: GUC patch for Win32