| From: | "Ed L(dot)" <pggeneral(at)bluepolka(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Laurette Cisneros <laurette(at)nextbus(dot)com>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: server won't shutdown |
| Date: | 2003-02-18 00:24:20 |
| Message-ID: | 200302171724.20022.pggeneral@bluepolka.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Monday February 17 2003 5:09, Tom Lane wrote:
> "Ed L." <pgadmin(at)bluepolka(dot)net> writes:
> > I've been seeing the same problem intermittently over the past 2
> > years among ~30 production clusters.
>
> Hm, I suddenly have a theory. Do you guys use LISTEN/NOTIFY in the
> databases that are exhibiting the problem? Is it possible that the
> backends that aren't cooperating have not done anything since they
> last received a NOTIFY? (That would imply that the connected
> frontend didn't issue any SQL commands in response to the
> notification.)
Not using LISTEN/NOTIFY here, at least not of which I'm aware. I'll
dig a little more and let you know if I find differently.
Ed
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ed L. | 2003-02-18 01:25:48 | Re: please help--database just locks up. |
| Previous Message | Tom Lane | 2003-02-18 00:09:43 | Re: server won't shutdown |