Re: Possible problem with pg_reload_conf() and view pg_settings

From: "Qingqing Zhou" <zhouqq(at)cs(dot)toronto(dot)edu>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Possible problem with pg_reload_conf() and view pg_settings
Date: 2005-11-05 03:36:51
Message-ID: dkh9bu$qon$1@news.hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2005-11-05 03:48:49 Re: somebody could explain this?
Previous Message Tom Lane 2005-11-05 03:10:38 Re: Possible problem with pg_reload_conf() and view pg_settings