Postgres Pro
Downloads
Home   >   mailing lists

Re: Possible problem with pg_reload_conf() and view pg_settings - Mailing list pgsql-hackers

From Qingqing Zhou
Subject Re: Possible problem with pg_reload_conf() and view pg_settings
Date
Msg-id dkh9bu$qon$1@news.hub.org
Whole thread Raw
In response to Possible problem with pg_reload_conf() and view pg_settings  (Tony Caduto <tony_caduto@amsoftwaredesign.com>)
List pgsql-hackers
Tree view 
"Tom Lane" <tgl@sss.pgh.pa.us> wrote
>
> Hmm, some delay in the signal being recognized in our Win32 signal
> implementation?  Why would that be?
>

I believe this is a disease for all platforms, not only Windows. This is 
because the signals are asynchoronized. Think when you returned from 
kill(SIGHUP), you can't suppose that Postmaster already got it. Now when you 
do your next command very fast, then there is a chance you didn't receive 
the forwarded SIGHUP from Postmaster. But windows does make the disease 
easier to be seen.

Regards,
Qingqing

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Possible problem with pg_reload_conf() and view pg_settings
Next
From: "Qingqing Zhou"
Date:
Subject: Re: postgresql-8.1RC1 on Solaris 10, amd64x2