| From: | Sergey Konoplev <sergey(dot)konoplev(at)postgresql-consulting(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Brian McNally <bmcnally(at)uw(dot)edu>, raghu ram <raghuchennuru(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Problem running "ALTER TABLE...", ALTER TABLE waiting |
| Date: | 2012-08-09 07:30:04 |
| Message-ID: | CAL_0b1vo4ritm3eH83e72mmp3J+Nnfj5kmDbZHE6GoOhqdYzPQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Aug 9, 2012 at 4:58 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Brian McNally <bmcnally(at)uw(dot)edu> writes:
>> Ok, I'm running with all available updates and kernel 2.6.18-308.4.1.el5
>> but am still having the same problem.
>
> It's fairly clearly blocked on a lock ... have you looked into the
> pg_locks view to see what is holding the lock?
There is a hidden part of the conversation. We have already checked
pg_locks and no locks were there. Moreover there were no other
activity except the ALTER. And this was the odd part.
> (I'm wondering about a prepared transaction, myself. There isn't much
> else that could hold a lock across a server restart.)
Are not they shown by pg_locks?
>
> regards, tom lane
--
Sergey Konoplev
a database architect, software developer at PostgreSQL-Consulting.com
http://www.postgresql-consulting.com
Jabber: gray(dot)ru(at)gmail(dot)com Skype: gray-hemp Phone: +79160686204
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stefan Keller | 2012-08-09 11:32:43 | Expression alias not recognized in WHERE clause (ERROR: relation "p" does not exist) |
| Previous Message | Marc Mamin | 2012-08-09 07:19:26 | Re: processing large amount of rows with plpgsql |