Re: forced to restart postgresql service yesterday - Mailing list pgsql-hackers

From Tom Lane
Subject Re: forced to restart postgresql service yesterday
Date
Msg-id 10657.1134053453@sss.pgh.pa.us
Whole thread Raw
In response to forced to restart postgresql service yesterday  ("Merlin Moncure" <merlin.moncure@rcsonline.com>)
List pgsql-hackers
"Merlin Moncure" <merlin.moncure@rcsonline.com> writes:
> The login was hanging in a simple plpgsql login script which basically
> did an insert/update on a small table.  It would hang when called from
> within psql, and once hung the query would not respond to cancel
> requests (such as they are implemented on win32).  Investigating
> further, trying to select form this small table at all would also hang.
> Unfortunately, this table tells me which pids are safe to kill and which
> are not,

Did you look at pg_locks or pg_stat_activity?

There is pretty much nothing we can do with this report given the lack
of detail.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Reducing contention for the LockMgrLock
Next
From: Bruce Momjian
Date:
Subject: Re: Vertical Partitioning with TOAST