| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Chris Waters" <chris(dot)waters(at)networkchemistry(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Fixing stale locks |
| Date: | 2002-12-15 05:27:17 |
| Message-ID: | 5805.1039930037@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
"Chris Waters" <chris(dot)waters(at)networkchemistry(dot)com> writes:
> My first instinct was a stale lock so I look in pg_locks and sure enough a
> lock exists. Now the question is, how do I free this lock? This is just a
> single machine installation and there are no processes running that could
> hold the lock.
Oh? Exactly what process does pg_locks show is holding the lock then?
> How do people normally deal with this type of problem?
Either you're misdescribing it, or it's not a normal type of problem.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | jonesrf1 | 2002-12-15 16:36:05 | 7.2.3 build fails --with-java |
| Previous Message | Jesus Sandoval | 2002-12-15 01:14:39 | Re: Database maintenance help |