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

Commiteb03cff

Browse files
committed
Documentation improvements for pg_locks with respect to SSI.
Explain that querying pg_locks does not simultaneously lock both thenormal lock manager and the predicate lock manager.Per discussion with Kevin Grittner.
1 parent194e6ee commiteb03cff

File tree

1 file changed

+12
-7
lines changed

1 file changed

+12
-7
lines changed

‎doc/src/sgml/catalogs.sgml

Lines changed: 12 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -7085,13 +7085,18 @@
70857085
</para>
70867086

70877087
<para>
7088-
When the <structname>pg_locks</structname> view is accessed, the
7089-
internal lock manager data structures are momentarily locked, and
7090-
a copy is made for the view to display. This ensures that the
7091-
view produces a consistent set of results, while not blocking
7092-
normal lock manager operations longer than necessary. Nonetheless
7093-
there could be some impact on database performance if this view is
7094-
frequently accessed.
7088+
The <structname>pg_locks</structname> view displays data from both the
7089+
regular lock manager and the predicate lock manager, which are
7090+
separate systems. When this view is accessed, the internal data
7091+
structures of each lock manager are momentarily locked, and copies are
7092+
made for the view to display. Each lock manager will therefore
7093+
produce a consistent set of results, but as we do not lock both lock
7094+
managers simultaneously, it is possible for locks to be taken or
7095+
released after we interrogate the regular lock manager and before we
7096+
interrogate the predicate lock manager. Each lock manager is only
7097+
locked for the minimum possible time so as to reduce the performance
7098+
impact of querying this view, but there could nevertheless be some
7099+
impact on database performance if it is frequently accessed.
70957100
</para>
70967101

70977102
<para>

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp