From: | "Ed L(dot)" <pgsql(at)bluepolka(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Ed L(dot)" <pggeneral(at)bluepolka(dot)net>, Laurette Cisneros <laurette(at)nextbus(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: server won't shutdown |
Date: | 2003-02-20 01:11:33 |
Message-ID: | 200302191811.33796.pgsql@bluepolka.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Monday February 17 2003 8:06, Tom Lane wrote:
>
> Attached is the fix against 7.3 (or CVS tip). The same bug exists
> in 7.2 and 7.1, and should be fixable by the same patch (possibly
> with some fuzz).
>
> You can demonstrate the problem by doing 'LISTEN foo' in one psql
> and then 'NOTIFY foo' in another, then attempting a fast shutdown
> --- the first psql's backend will ignore you until the psql session
> does something. The same path can be followed without LISTEN if the
> first psql is simply left idle while the second one does a bunch of
> catalog-updating work (a few cycles of VACUUM ANALYZE usually
> suffice).
I have verified this fixed the problem on 7.2.4 in the case of the
latter VACUUM ANALYZE example, and will test it also against 7.3.2
before too long. Thanks again, Tom.
Ed
From | Date | Subject | |
---|---|---|---|
Next Message | Yudha Setiawan | 2003-02-20 02:29:00 | Re: How to avoid the Mutating Triggers ?? |
Previous Message | Stephan Szabo | 2003-02-19 19:29:40 | Re: pg_dumpall |