From: | Samuel Stearns <SStearns(at)internode(dot)com(dot)au> |
---|---|
To: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: ALTER TABLE <name> ADD COLUMN Hangs |
Date: | 2010-04-22 22:56:15 |
Message-ID: | 68B59BEDCD36854AADBDF17E91B2937A01A4DC6401@EXCHMAIL.staff.internode.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Thanks Ross and Scott. I got it to complete finally thanks to Ross' tip of looking at pg_locks. I had to kill a few processes with exclusive locks on the table and then presto!
Scott, the query didn't have a DEFAULT keyword with it and I've got a request in with our sysadmins to upgrade us to 8.3.10. Thanks both of you for all your help.
Sam
-----Original Message-----
From: Scott Marlowe [mailto:scott(dot)marlowe(at)gmail(dot)com]
Sent: Thursday, 22 April 2010 4:15 PM
To: Samuel Stearns
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: [ADMIN] ALTER TABLE <name> ADD COLUMN Hangs
On Wed, Apr 21, 2010 at 8:17 PM, Samuel Stearns
<SStearns(at)internode(dot)com(dot)au> wrote:
> Howdy,
>
> I'm running in an 8.3.3 environment. What could cause, or how can I
> diagnose, why an 'ALTER TABLE <name> ADD COLUMN' statement runs for hours
> eventually locking users out and requiring to be killed in the end?
And not that it matters here, but is there a reason for running such
out of date pgsql code?
From | Date | Subject | |
---|---|---|---|
Next Message | Edwin Quijada | 2010-04-23 03:26:42 | Re: [pgsql-es-ayuda] REF: Migracion de Sqlserver a Postgresql |
Previous Message | Pankaj Mandal (pmandal) | 2010-04-22 20:52:46 | Re: initdb failure |