| From: | Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec> |
|---|---|
| To: | Clayton Graf <clayton(dot)graf(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: AccessShareLock question |
| Date: | 2009-12-19 16:19:21 |
| Message-ID: | 3073cc9b0912190819x2f7045ael252b2c9d114e6640@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sat, Dec 19, 2009 at 10:58 AM, Clayton Graf <clayton(dot)graf(at)gmail(dot)com> wrote:
> Ok, but this is really my problem: I cannot perform an ALTER TABLE with the
> system in production mode, because the ALTER TABLE hangs due an
> AccessShareLock.
until the lock is released, are your selects all that long?
besides, why are you ALTERing the table in production... i guess
clients will suffer if the expect less or more columns than the ones
they receive from the ALTERed table
> We use two-tier mode,
don't understand this
> so is it necessary to shutdown all users before
> perform an ALTER TABLE?
no
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Postgres User | 2009-12-19 18:30:12 | Re: Selecting from table into an array var |
| Previous Message | Clayton Graf | 2009-12-19 15:58:12 | Re: AccessShareLock question |