| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Hanging VACUUM |
| Date: | 2001-05-26 05:26:39 |
| Message-ID: | 21999.990854799@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> I just noticed that if I do BEGIN;CREATE TABLE..., and then start VACUUM
> of the database in another psql session, the VACUUM hangs until the
> transaction completes. Is this expected?
Sure. You have a write lock on pg_class ... not to mention a few other
system tables, but that's the one this trace shows VACUUM is waiting for
exclusive lock on:
> #5 0x811b67a in LockRelation (relation=0x826b01c, lockmode=7) at lmgr.c:141
> #6 0x80735c5 in heap_open (relationId=1259, lockmode=7) at heapam.c:596
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oleg Bartunov | 2001-05-26 12:33:01 | First version of multi-key index support for GiST |
| Previous Message | Bruce Momjian | 2001-05-26 04:58:08 | Hanging VACUUM |