| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Creager <Robert_Creager(at)LogicalChaos(dot)org> |
| Cc: | PGBugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: 7.4b4 undetected deadlock? |
| Date: | 2003-10-06 00:34:15 |
| Message-ID: | 16190.1065400455@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Robert Creager <Robert_Creager(at)LogicalChaos(dot)org> writes:
> postgres 29304 20209 0 17:37 pts/4 00:00:00 postgres: robert tassiv 192.168.0.250 idle in transaction
Almost certainly, that guy is holding the lock REINDEX wants. The
VACUUM is probably backed up behind the REINDEX. If you want to
convince me it's a deadlock, you'll need to exhibit pg_locks contents.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Creager | 2003-10-06 00:43:25 | Re: 7.4b4 undetected deadlock? |
| Previous Message | ljb | 2003-10-06 00:21:45 | Re: 7.4beta4: make check broken? |