| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: forced to restart postgresql service yesterday |
| Date: | 2005-12-08 14:50:53 |
| Message-ID: | 10657.1134053453@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2005-12-08 15:03:43 | Re: Vertical Partitioning with TOAST |
| Previous Message | Tom Lane | 2005-12-08 14:44:35 | Re: Reducing contention for the LockMgrLock |