mirror of
https://git.postgresql.org/git/postgresql.git
synced 2025-02-05 19:09:58 +08:00
Make GetLockStatusData's header comment resemble reality.
The API spec for this function was changed completely (and for the better)
by commit 3cba8999b3
, but it didn't bother
with anything as mundane as updating the comments.
This commit is contained in:
parent
13a6fa3634
commit
9b92e76f7b
@ -3371,10 +3371,11 @@ LockShmemSize(void)
|
||||
* GetLockStatusData - Return a summary of the lock manager's internal
|
||||
* status, for use in a user-level reporting function.
|
||||
*
|
||||
* The return data consists of an array of PROCLOCK objects, with the
|
||||
* associated PGPROC and LOCK objects for each. Note that multiple
|
||||
* copies of the same PGPROC and/or LOCK objects are likely to appear.
|
||||
* It is the caller's responsibility to match up duplicates if wanted.
|
||||
* The return data consists of an array of LockInstanceData objects,
|
||||
* which are a lightly abstracted version of the PROCLOCK data structures,
|
||||
* i.e. there is one entry for each unique lock and interested PGPROC.
|
||||
* It is the caller's responsibility to match up related items (such as
|
||||
* references to the same lockable object or PGPROC) if wanted.
|
||||
*
|
||||
* The design goal is to hold the LWLocks for as short a time as possible;
|
||||
* thus, this function simply makes a copy of the necessary data and releases
|
||||
|
Loading…
Reference in New Issue
Block a user