Re: AccessShareLock question
| От | Clayton Graf |
|---|---|
| Тема | Re: AccessShareLock question |
| Дата | |
| Msg-id | 7b2fe65d0912190758m469a084bgf84595972ecdd0c@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: AccessShareLock question (Jaime Casanova <jcasanov@systemguards.com.ec>) |
| Ответы |
Re: AccessShareLock question
|
| Список | pgsql-general |
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.
--
Clayton Graf
We use two-tier mode, so is it necessary to shutdown all users before perform an ALTER TABLE? Is it this true?
Thanks,
Clayton
2009/12/19 Jaime Casanova <jcasanov@systemguards.com.ec>
On Sat, Dec 19, 2009 at 9:04 AM, Clayton Graf <clayton.graf@gmail.com> wrote:http://www.postgresql.org/docs/current/static/explicit-locking.html says:
> I get an AccessShareLock in a simple select command and I am not using the
> FOR SHARE clause.
"""
ACCESS SHARE
Conflicts with the ACCESS EXCLUSIVE lock mode only.
The SELECT command acquires a lock of this mode on referenced
tables. In general, any query that only reads a table and does not
modify it will acquire this lock mode.
"""
in other words, everything is ok, AccessShareLock doesn't block
anything but with anyone trying to change the structure of the table
(ALTER, DROP) and with commands TRUNCATE, REINDEX, CLUSTER, and VACUUM
FULL, and every select take it
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157
--
Clayton Graf
В списке pgsql-general по дате отправления: