mirror of
https://git.postgresql.org/git/postgresql.git
synced 2025-02-11 19:20:40 +08:00
Fix inconsistency in pg_buffercache docs.
Commit 6e654546fb
avoids locking bufmgr partitions to make pg_buffercache
less disruptive on production systems but forgot to update the docs.
Reported-by: Sawada Masahiko
Author: Sawada Masahiko
Reviewed-by: Amit Kapila
Backpatch-through: 10
Discussion: https://postgr.es/m/CA+fd4k6sD8oeP1qJbFAor=rCpYckU9DsywHiYx3x5Hz5Z8Ua_w@mail.gmail.com
This commit is contained in:
parent
f2ff203596
commit
f9463d2a90
@ -135,12 +135,11 @@
|
||||
</para>
|
||||
|
||||
<para>
|
||||
When the <structname>pg_buffercache</structname> view is accessed, internal buffer
|
||||
manager locks are taken for long enough to copy all the buffer state
|
||||
data that the view will display.
|
||||
This ensures that the view produces a consistent set of results, while not
|
||||
blocking normal buffer activity longer than necessary. Nonetheless there
|
||||
could be some impact on database performance if this view is read often.
|
||||
Since buffer manager locks are not taken to copy the buffer state data that
|
||||
the view will display, accessing <structname>pg_buffercache</structname> view
|
||||
has less impact on normal buffer activity but it doesn't provide a consistent
|
||||
set of results across all buffers. However, we ensure that the information of
|
||||
each buffer is self-consistent.
|
||||
</para>
|
||||
</sect2>
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user