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

Commitf9463d2

Browse files
author
Amit Kapila
committed
Fix inconsistency in pg_buffercache docs.
Commit6e65454 avoids locking bufmgr partitions to make pg_buffercacheless disruptive on production systems but forgot to update the docs.Reported-by: Sawada MasahikoAuthor: Sawada MasahikoReviewed-by: Amit KapilaBackpatch-through: 10Discussion:https://postgr.es/m/CA+fd4k6sD8oeP1qJbFAor=rCpYckU9DsywHiYx3x5Hz5Z8Ua_w@mail.gmail.com
1 parentf2ff203 commitf9463d2

File tree

1 file changed

+5
-6
lines changed

1 file changed

+5
-6
lines changed

‎doc/src/sgml/pgbuffercache.sgml

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -135,12 +135,11 @@
135135
</para>
136136

137137
<para>
138-
When the <structname>pg_buffercache</structname> view is accessed, internal buffer
139-
manager locks are taken for long enough to copy all the buffer state
140-
data that the view will display.
141-
This ensures that the view produces a consistent set of results, while not
142-
blocking normal buffer activity longer than necessary. Nonetheless there
143-
could be some impact on database performance if this view is read often.
138+
Since buffer manager locks are not taken to copy the buffer state data that
139+
the view will display, accessing <structname>pg_buffercache</structname> view
140+
has less impact on normal buffer activity but it doesn't provide a consistent
141+
set of results across all buffers. However, we ensure that the information of
142+
each buffer is self-consistent.
144143
</para>
145144
</sect2>
146145

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp