Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit9b92e76

Browse files
committed
Make GetLockStatusData's header comment resemble reality.
The API spec for this function was changed completely (and for the better)by commit3cba899, but it didn't botherwith anything as mundane as updating the comments.
1 parent13a6fa3 commit9b92e76

File tree

1 file changed

+5
-4
lines changed
  • src/backend/storage/lmgr

1 file changed

+5
-4
lines changed

‎src/backend/storage/lmgr/lock.c

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -3371,10 +3371,11 @@ LockShmemSize(void)
33713371
* GetLockStatusData - Return a summary of the lock manager's internal
33723372
* status, for use in a user-level reporting function.
33733373
*
3374-
* The return data consists of an array of PROCLOCK objects, with the
3375-
* associated PGPROC and LOCK objects for each. Note that multiple
3376-
* copies of the same PGPROC and/or LOCK objects are likely to appear.
3377-
* It is the caller's responsibility to match up duplicates if wanted.
3374+
* The return data consists of an array of LockInstanceData objects,
3375+
* which are a lightly abstracted version of the PROCLOCK data structures,
3376+
* i.e. there is one entry for each unique lock and interested PGPROC.
3377+
* It is the caller's responsibility to match up related items (such as
3378+
* references to the same lockable object or PGPROC) if wanted.
33783379
*
33793380
* The design goal is to hold the LWLocks for as short a time as possible;
33803381
* thus, this function simply makes a copy of the necessary data and releases

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp