| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Brad Nicholson <bnichols(at)ca(dot)afilias(dot)info> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, dba <dba(at)ca(dot)afilias(dot)info> |
| Subject: | Re: Vacuum Blocking A Deleteion - Why? |
| Date: | 2006-01-04 22:17:14 |
| Message-ID: | 8624.1136413034@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Brad Nicholson <bnichols(at)ca(dot)afilias(dot)info> writes:
> We have been having a problem with a long running vacuum on a table
> blocking deletes. We have a log table on which the only activity is an
> on going series of deletions. The problem is experienced on a slony
> replicated node, but I don't think that slony is at fault here.
> My question - why is a vacuum blocking a deletion?
The problem is evidently that it's got an exclusive lock on the table:
> 17578 | 1744920 | AccessExclusiveLock | t
which is entirely unexpected behavior for plain VACUUM in any release
later than 7.1. I have to think that slony does have something to do
with it ... would suggest asking the slony folk about this.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-01-04 23:22:59 | back-patching locale environment fix |
| Previous Message | Brad Nicholson | 2006-01-04 21:23:05 | Vacuum Blocking A Deleteion - Why? |