Re: pgsql: Fix Win32 problems with signals and sockets,

"Marc G. Fournier" <scrappy(at)postgresql(dot)org> writes:
> Is this the big one we were waiting on for the new beta? or is something
> else in the queue being waited on?

This is the biggie I think, but there were ten or so other minor patches
in the queue that I hope to get to tomorrow. Maybe plan on wrapping
beta5 tomorrow evening?

regards, tom lane

> On Wed, 17 Nov 2004, Tom Lane wrote:

>> Log Message:
>> -----------
>> Fix Win32 problems with signals and sockets, by making the forkexec code
>> even uglier than it was already :-(. Also, on Windows only, use temporary
>> shared memory segments instead of ordinary files to pass over critical
>> variable values from postmaster to child processes. Magnus Hagander
>>
>> Modified Files:
>> --------------
>> pgsql/src/backend/main:
>> main.c (r1.92 -> r1.93)
>> (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/main/main.c.diff?r1=1.92&r2=1.93)
>> pgsql/src/backend/port/win32:
>> signal.c (r1.9 -> r1.10)
>> (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/port/win32/signal.c.diff?r1=1.9&r2=1.10)
>> pgsql/src/backend/postmaster:
>> pgstat.c (r1.84 -> r1.85)
>> (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/postmaster/pgstat.c.diff?r1=1.84&r2=1.85)
>> postmaster.c (r1.438 -> r1.439)
>> (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/postmaster/postmaster.c.diff?r1=1.438&r2=1.439)
>> pgsql/src/include/port:
>> win32.h (r1.39 -> r1.40)
>> (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/port/win32.h.diff?r1=1.39&r2=1.40)
>>
>> ---------------------------(end of broadcast)---------------------------
>> TIP 7: don't forget to increase your free space map settings
>>

> ----
> Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
> Email: scrappy(at)hub(dot)org Yahoo!: yscrappy ICQ: 7615664

> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?

> http://www.postgresql.org/docs/faqs/FAQ.html