I see this pretty often on 7.1b4, running on redhat linux 6.2 (or 7.0;
same problem on both). My lockups are always either INSERT or UPDATE,
and all the other backends are shown as "idle in transaction".
I've been trying to track this down, but haven't had any luck.
Suggestions?
Thanks,
-Randy
> -----Original Message-----
> From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
> Sent: Thursday, April 05, 2001 4:12 PM
> To: Maurice Balick
> Cc: pgsql-general@postgresql.org
> Subject: Re: [GENERAL] locked up backends
>
>
> Maurice Balick <balm@smiley.com> writes:
> > We are running Postgres 7.0.2 on Linux RH 6.2 Dell servers.
>
> > When traffic gets heavy we often get one of the backend
> locked up in an
> > UPDATE, INSERT or COMMIT request. Eventually all the other
> backends end
> > up locking too as they try to access a row locked by the original
> > backend.
>
> Try updating to 7.0.3. You may be getting caught by 7.0.2's
> failure to
> release locks when a client disconnects partway through a transaction
> block.
>
> If you still see this in 7.0.3 then it'd be worth further
> investigation.
>
> regards, tom lane
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
>