| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Dan Armbrust" <daniel(dot)armbrust(dot)list(at)gmail(dot)com> |
| Cc: | "Erik Jones" <erik(at)myemma(dot)com>, "pgsql general" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Deadlock situation? |
| Date: | 2008-04-30 15:33:35 |
| Message-ID: | 19183.1209569615@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Dan Armbrust" <daniel(dot)armbrust(dot)list(at)gmail(dot)com> writes:
>> What sort of indexes are there on this table?
> [ just btrees ]
Okay, that lets the GIN stuff off the hook.
I wonder whether you saw some variant of the deadlock reported in bug
#3883 --- see discussion here:
http://archives.postgresql.org/pgsql-hackers/2008-01/msg00873.php
The only known way of getting into that problem is fixed in 8.3,
but a potential for silent deadlock is definitely still there.
I don't however have any idea how such a deadlock could occur without
at least some processes showing as 'waiting' in pg_stat_activity.
Do you have any idea what the transactions that were blocked at
COMMIT had been doing?
Are there any foreign key constraints leading *to* this table?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joseph S | 2008-04-30 15:52:09 | Re: Why is postgres autovacuuming a table that is never updated? |
| Previous Message | Andrew Sullivan | 2008-04-30 15:20:50 | Re: How to modify ENUM datatypes? |