definer function.) Also, heavy concurrent use of row share locks on the
referenced table could pose a performance problem, especially if updates
of it are frequent. Another solution, practical if updates of the
- referenced table are infrequent, is to take an exclusive lock on the
+ referenced table are infrequent, is to take an
+ ACCESS EXCLUSIVE lock on the
referenced table when updating it, so that no concurrent transactions
could be examining old row values. Or one could just wait for all
concurrent transactions to end after committing an update of the
ALTER TABLE tablename ALTER hstorecol TYPE hstore USING hstorecol || '';
- The ALTER TABLE method requires an exclusive lock on the table,
+ The ALTER TABLE method requires an
+ ACCESS EXCLUSIVE lock on the table,
but does not result in bloating the table with old row versions.
RowExclusiveLock when updating the index (including plain
VACUUM). Since these lock types do not conflict, the access
method is responsible for handling any fine-grained locking it might need.
- An exclusive lock on the index as a whole will be taken only during index
- creation, destruction, or REINDEX.
+ An ACCESS EXCLUSIVE lock on the index as a whole will be
+ taken only during index creation, destruction, or REINDEX
+ (SHARE UPDATE EXCLUSIVE is taken instead with
+ CONCURRENTLY).
DELETE will continue to function normally, though you
will not be able to modify the definition of a table with commands such as
ALTER TABLE while it is being vacuumed.)
- VACUUM FULL requires exclusive lock on the table it is
+ VACUUM FULL requires an
+ ACCESS EXCLUSIVE lock on the table it is
working on, and therefore cannot be done in parallel with other use
of the table. Generally, therefore,
administrators should strive to use standard VACUUM and
or one of the table-rewriting variants of
.
These commands rewrite an entire new copy of the table and build
- new indexes for it. All these options require exclusive lock. Note that
+ new indexes for it. All these options require an
+ ACCESS EXCLUSIVE lock. Note that
they also temporarily use extra disk space approximately equal to the size
of the table, since the old copies of the table and indexes can't be
released until the new ones are complete.
tables are not dropped or modified in incompatible ways while the
command executes. (For example, TRUNCATE cannot safely be
executed concurrently with other operations on the same table, so it
- obtains an exclusive lock on the table to enforce that.)
+ obtains an ACCESS EXCLUSIVE lock on the table to
+ enforce that.)
- If the table as a whole is exclusive-locked by someone else,
- pgrowlocks will be blocked.
+ If an ACCESS EXCLUSIVE lock is taken on the table,
+ pgrowlocks will be blocked.
Drop the index without locking out concurrent selects, inserts, updates,
and deletes on the index's table. A normal DROP INDEX
- acquires an exclusive lock on the table, blocking other accesses until the
- index drop can be completed. With this option, the command instead
- waits until conflicting transactions have completed.
+ acquires an ACCESS EXCLUSIVE lock on the table,
+ blocking other accesses until the index drop can be completed. With
+ this option, the command instead waits until conflicting transactions
+ have completed.
There are several caveats to be aware of when using this option.
REINDEX is similar to a drop and recreate of the index
in that the index contents are rebuilt from scratch. However, the locking
considerations are rather different. REINDEX locks out writes
- but not reads of the index's parent table. It also takes an exclusive lock
- on the specific index being processed, which will block reads that attempt
- to use that index. In contrast, DROP INDEX momentarily takes
- an exclusive lock on the parent table, blocking both writes and reads. The
- subsequent CREATE INDEX locks out writes but not reads; since
- the index is not there, no read will attempt to use it, meaning that there
- will be no blocking but reads might be forced into expensive sequential
- scans.
+ but not reads of the index's parent table. It also takes an
+ ACCESS EXCLUSIVE lock on the specific index being processed,
+ which will block reads that attempt to use that index. In contrast,
+ DROP INDEX momentarily takes an
+ ACCESS EXCLUSIVE lock on the parent table, blocking both
+ writes and reads. The subsequent CREATE INDEX locks out
+ writes but not reads; since the index is not there, no read will attempt to
+ use it, meaning that there will be no blocking but reads might be forced
+ into expensive sequential scans.
same table. VACUUM FULL rewrites the entire contents
of the table into a new disk file with no extra space, allowing unused
space to be returned to the operating system. This form is much slower and
- requires an exclusive lock on each table while it is being processed.
+ requires an ACCESS EXCLUSIVE lock on each table while
+ it is being processed.
projects / postgresql.git / commitdiff