1996-08-28 03:59:28 +02:00
|
|
|
/*-------------------------------------------------------------------------
|
|
|
|
*
|
1999-02-14 00:22:53 +01:00
|
|
|
* lmgr.h
|
1997-09-07 07:04:48 +02:00
|
|
|
* POSTGRES lock manager definitions.
|
1996-08-28 03:59:28 +02:00
|
|
|
*
|
|
|
|
*
|
2014-01-07 22:05:30 +01:00
|
|
|
* Portions Copyright (c) 1996-2014, PostgreSQL Global Development Group
|
2000-01-26 06:58:53 +01:00
|
|
|
* Portions Copyright (c) 1994, Regents of the University of California
|
1996-08-28 03:59:28 +02:00
|
|
|
*
|
2010-09-20 22:08:53 +02:00
|
|
|
* src/include/storage/lmgr.h
|
1996-08-28 03:59:28 +02:00
|
|
|
*
|
|
|
|
*-------------------------------------------------------------------------
|
|
|
|
*/
|
1997-09-07 07:04:48 +02:00
|
|
|
#ifndef LMGR_H
|
1996-08-28 03:59:28 +02:00
|
|
|
#define LMGR_H
|
|
|
|
|
2007-06-19 22:13:22 +02:00
|
|
|
#include "lib/stringinfo.h"
|
2008-05-12 02:00:54 +02:00
|
|
|
#include "storage/itemptr.h"
|
1999-07-16 01:04:24 +02:00
|
|
|
#include "storage/lock.h"
|
|
|
|
#include "utils/rel.h"
|
1996-08-28 03:59:28 +02:00
|
|
|
|
2005-04-30 21:03:33 +02:00
|
|
|
|
Setup error context callback for transaction lock waits
With this in place, a session blocking behind another one because of
tuple locks will get a context line mentioning the relation name, tuple
TID, and operation being done on tuple. For example:
LOG: process 11367 still waiting for ShareLock on transaction 717 after 1000.108 ms
DETAIL: Process holding the lock: 11366. Wait queue: 11367.
CONTEXT: while updating tuple (0,2) in relation "foo"
STATEMENT: UPDATE foo SET value = 3;
Most usefully, the new line is displayed by log entries due to
log_lock_waits, although of course it will be printed by any other log
message as well.
Author: Christian Kruse, some tweaks by Álvaro Herrera
Reviewed-by: Amit Kapila, Andres Freund, Tom Lane, Robert Haas
2014-03-19 19:10:36 +01:00
|
|
|
/* XactLockTableWait operations */
|
|
|
|
typedef enum XLTW_Oper
|
|
|
|
{
|
|
|
|
XLTW_None,
|
|
|
|
XLTW_Update,
|
|
|
|
XLTW_Delete,
|
|
|
|
XLTW_Lock,
|
|
|
|
XLTW_LockUpdated,
|
|
|
|
XLTW_InsertIndex,
|
|
|
|
XLTW_InsertIndexUnique,
|
|
|
|
XLTW_FetchUpdated,
|
|
|
|
XLTW_RecheckExclusionConstr
|
|
|
|
} XLTW_Oper;
|
|
|
|
|
1997-09-08 04:41:22 +02:00
|
|
|
extern void RelationInitLockInfo(Relation relation);
|
1996-08-28 03:59:28 +02:00
|
|
|
|
2000-12-22 01:51:54 +01:00
|
|
|
/* Lock a relation */
|
2006-07-31 22:09:10 +02:00
|
|
|
extern void LockRelationOid(Oid relid, LOCKMODE lockmode);
|
|
|
|
extern bool ConditionalLockRelationOid(Oid relid, LOCKMODE lockmode);
|
|
|
|
extern void UnlockRelationId(LockRelId *relid, LOCKMODE lockmode);
|
2006-08-18 18:09:13 +02:00
|
|
|
extern void UnlockRelationOid(Oid relid, LOCKMODE lockmode);
|
2006-07-31 22:09:10 +02:00
|
|
|
|
1998-12-15 13:47:01 +01:00
|
|
|
extern void LockRelation(Relation relation, LOCKMODE lockmode);
|
2001-06-22 02:04:59 +02:00
|
|
|
extern bool ConditionalLockRelation(Relation relation, LOCKMODE lockmode);
|
1998-12-15 13:47:01 +01:00
|
|
|
extern void UnlockRelation(Relation relation, LOCKMODE lockmode);
|
Fix performance problems with autovacuum truncation in busy workloads.
In situations where there are over 8MB of empty pages at the end of
a table, the truncation work for trailing empty pages takes longer
than deadlock_timeout, and there is frequent access to the table by
processes other than autovacuum, there was a problem with the
autovacuum worker process being canceled by the deadlock checking
code. The truncation work done by autovacuum up that point was
lost, and the attempt tried again by a later autovacuum worker. The
attempts could continue indefinitely without making progress,
consuming resources and blocking other processes for up to
deadlock_timeout each time.
This patch has the autovacuum worker checking whether it is
blocking any other thread at 20ms intervals. If such a condition
develops, the autovacuum worker will persist the work it has done
so far, release its lock on the table, and sleep in 50ms intervals
for up to 5 seconds, hoping to be able to re-acquire the lock and
try again. If it is unable to get the lock in that time, it moves
on and a worker will try to continue later from the point this one
left off.
While this patch doesn't change the rules about when and what to
truncate, it does cause the truncation to occur sooner, with less
blocking, and with the consumption of fewer resources when there is
contention for the table's lock.
The only user-visible change other than improved performance is
that the table size during truncation may change incrementally
instead of just once.
This problem exists in all supported versions but is infrequently
reported, although some reports of performance problems when
autovacuum runs might be caused by this. Initial commit is just the
master branch, but this should probably be backpatched once the
build farm and general developer usage confirm that there are no
surprising effects.
Jan Wieck
2012-12-11 21:33:08 +01:00
|
|
|
extern bool LockHasWaitersRelation(Relation relation, LOCKMODE lockmode);
|
1996-08-28 03:59:28 +02:00
|
|
|
|
2006-07-31 22:09:10 +02:00
|
|
|
extern void LockRelationIdForSession(LockRelId *relid, LOCKMODE lockmode);
|
|
|
|
extern void UnlockRelationIdForSession(LockRelId *relid, LOCKMODE lockmode);
|
2000-12-22 01:51:54 +01:00
|
|
|
|
2005-04-30 00:28:24 +02:00
|
|
|
/* Lock a relation for extension */
|
|
|
|
extern void LockRelationForExtension(Relation relation, LOCKMODE lockmode);
|
|
|
|
extern void UnlockRelationForExtension(Relation relation, LOCKMODE lockmode);
|
|
|
|
|
|
|
|
/* Lock a page (currently only used within indexes) */
|
1998-12-15 13:47:01 +01:00
|
|
|
extern void LockPage(Relation relation, BlockNumber blkno, LOCKMODE lockmode);
|
2003-09-05 00:06:27 +02:00
|
|
|
extern bool ConditionalLockPage(Relation relation, BlockNumber blkno, LOCKMODE lockmode);
|
1998-12-15 13:47:01 +01:00
|
|
|
extern void UnlockPage(Relation relation, BlockNumber blkno, LOCKMODE lockmode);
|
1996-08-28 03:59:28 +02:00
|
|
|
|
2005-04-30 21:03:33 +02:00
|
|
|
/* Lock a tuple (see heap_lock_tuple before assuming you understand this) */
|
|
|
|
extern void LockTuple(Relation relation, ItemPointer tid, LOCKMODE lockmode);
|
2005-08-01 22:31:16 +02:00
|
|
|
extern bool ConditionalLockTuple(Relation relation, ItemPointer tid,
|
2005-10-15 04:49:52 +02:00
|
|
|
LOCKMODE lockmode);
|
2005-04-30 21:03:33 +02:00
|
|
|
extern void UnlockTuple(Relation relation, ItemPointer tid, LOCKMODE lockmode);
|
|
|
|
|
2000-12-22 01:51:54 +01:00
|
|
|
/* Lock an XID (used to wait for a transaction to finish) */
|
1998-12-15 13:47:01 +01:00
|
|
|
extern void XactLockTableInsert(TransactionId xid);
|
2004-09-16 18:58:44 +02:00
|
|
|
extern void XactLockTableDelete(TransactionId xid);
|
Setup error context callback for transaction lock waits
With this in place, a session blocking behind another one because of
tuple locks will get a context line mentioning the relation name, tuple
TID, and operation being done on tuple. For example:
LOG: process 11367 still waiting for ShareLock on transaction 717 after 1000.108 ms
DETAIL: Process holding the lock: 11366. Wait queue: 11367.
CONTEXT: while updating tuple (0,2) in relation "foo"
STATEMENT: UPDATE foo SET value = 3;
Most usefully, the new line is displayed by log entries due to
log_lock_waits, although of course it will be printed by any other log
message as well.
Author: Christian Kruse, some tweaks by Álvaro Herrera
Reviewed-by: Amit Kapila, Andres Freund, Tom Lane, Robert Haas
2014-03-19 19:10:36 +01:00
|
|
|
extern void XactLockTableWait(TransactionId xid, Relation rel,
|
|
|
|
ItemPointer ctid, XLTW_Oper oper);
|
2005-08-01 22:31:16 +02:00
|
|
|
extern bool ConditionalXactLockTableWait(TransactionId xid);
|
2001-10-28 07:26:15 +01:00
|
|
|
|
2013-09-27 16:46:33 +02:00
|
|
|
/* Lock VXIDs, specified by conflicting locktags */
|
|
|
|
extern void WaitForLockers(LOCKTAG heaplocktag, LOCKMODE lockmode);
|
|
|
|
extern void WaitForLockersMultiple(List *locktags, LOCKMODE lockmode);
|
|
|
|
|
2005-04-30 21:03:33 +02:00
|
|
|
/* Lock a general object (other than a relation) of the current database */
|
|
|
|
extern void LockDatabaseObject(Oid classid, Oid objid, uint16 objsubid,
|
2005-10-15 04:49:52 +02:00
|
|
|
LOCKMODE lockmode);
|
2005-04-30 21:03:33 +02:00
|
|
|
extern void UnlockDatabaseObject(Oid classid, Oid objid, uint16 objsubid,
|
2005-10-15 04:49:52 +02:00
|
|
|
LOCKMODE lockmode);
|
2005-04-30 21:03:33 +02:00
|
|
|
|
|
|
|
/* Lock a shared-across-databases object (other than a relation) */
|
|
|
|
extern void LockSharedObject(Oid classid, Oid objid, uint16 objsubid,
|
2005-10-15 04:49:52 +02:00
|
|
|
LOCKMODE lockmode);
|
2005-04-30 21:03:33 +02:00
|
|
|
extern void UnlockSharedObject(Oid classid, Oid objid, uint16 objsubid,
|
2005-10-15 04:49:52 +02:00
|
|
|
LOCKMODE lockmode);
|
2005-04-30 21:03:33 +02:00
|
|
|
|
2008-11-07 19:25:07 +01:00
|
|
|
extern void LockSharedObjectForSession(Oid classid, Oid objid, uint16 objsubid,
|
2009-06-11 16:49:15 +02:00
|
|
|
LOCKMODE lockmode);
|
2008-11-07 19:25:07 +01:00
|
|
|
extern void UnlockSharedObjectForSession(Oid classid, Oid objid, uint16 objsubid,
|
2009-06-11 16:49:15 +02:00
|
|
|
LOCKMODE lockmode);
|
2008-11-07 19:25:07 +01:00
|
|
|
|
2007-06-19 22:13:22 +02:00
|
|
|
/* Describe a locktag for error messages */
|
|
|
|
extern void DescribeLockTag(StringInfo buf, const LOCKTAG *tag);
|
|
|
|
|
2001-11-05 18:46:40 +01:00
|
|
|
#endif /* LMGR_H */
|