From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: GUC patch for Win32 |
Date: | 2003-05-03 19:26:58 |
Message-ID: | 200305031926.h43JQwT07103@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Peter Eisentraut wrote:
> What about all the other global variables? Will there be a separate
> mechanism for each kind?
Good question. I am not sure yet. I figured I would hit the GUC ones
first because they are easy and all in one place, then see what others
exist in the Peer Direct patch.
Did I hit all the GUC structure members that need to be dumped --- name,
value, source?
>
> Bruce Momjian writes:
>
> > Here is a patch that saves the postmaster GUC state into a file to be
> > read in by exec'ed backends. This is a start toward a fork/exec option
> > for Unix (for testing) and a CreateProcess option for Win32.
> >
> > The patch basically writes all modified GUC variables to a binary file
> > that can be read in by newly created exec'ed backends.
--
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
From | Date | Subject | |
---|---|---|---|
Next Message | Barry Lind | 2003-05-03 21:35:51 | Re: refcursor result set patch |
Previous Message | Peter Eisentraut | 2003-05-03 17:45:52 | Re: GUC patch for Win32 |