| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Steve Horn <steve(at)stevehorn(dot)cc> |
| Cc: | Devrim GÜNDÜZ <devrim(at)gunduz(dot)org>, pgsql-novice(at)postgresql(dot)org |
| Subject: | Re: Cannot DROP while process running |
| Date: | 2012-04-09 23:18:00 |
| Message-ID: | 15349.1334013480@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
Steve Horn <steve(at)stevehorn(dot)cc> writes:
> I ran this command:
> select pg_class.relname,pg_locks.* from pg_class,pg_locks where
> pg_class.relfilenode=pg_locks.relation;
> and it appears that almost every table in my database has
> ""AccessShareLock". I have read that those locks are placed on tables for
> SELECT access.
Well, an AccessShareLock would definitely prevent you from dropping the
table. The question is which session(s) are holding such locks and why.
I suspect that you have some long-running transactions, perhaps
accidentally so. As Devrim mentioned, joining pg_locks against
pg_stat_activity would go a long way towards explaining what's blocking
your DROP attempt.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steve Horn | 2012-04-10 12:58:10 | Re: Cannot DROP while process running |
| Previous Message | Steve Horn | 2012-04-09 21:07:35 | Re: Cannot DROP while process running |