Re: AccessShareLock question - Mailing list pgsql-general

From Jaime Casanova
Subject Re: AccessShareLock question
Date
Msg-id 3073cc9b0912190734t118cabd0va900d9d53cb812c3@mail.gmail.com
Whole thread Raw
In response to AccessShareLock question  (Clayton Graf <clayton.graf@gmail.com>)
Responses Re: AccessShareLock question
List pgsql-general
On Sat, Dec 19, 2009 at 9:04 AM, Clayton Graf <clayton.graf@gmail.com> wrote:
> I get an AccessShareLock in a simple select command and I am not using the
> FOR SHARE clause.

http://www.postgresql.org/docs/current/static/explicit-locking.html says:
"""
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

pgsql-general by date:

Previous
From: Chris Ernst
Date:
Subject: Re: Extracting SQL from logs in a usable format
Next
From: Clayton Graf
Date:
Subject: Re: AccessShareLock question