diff options
| author | Amit Kapila <akapila@postgresql.org> | 2020-05-08 09:07:14 +0530 |
|---|---|---|
| committer | Amit Kapila <akapila@postgresql.org> | 2020-05-08 09:07:14 +0530 |
| commit | b50712ba7530361a345ae01e5d929b3e6f46a0dc (patch) | |
| tree | cb8e4784ac39b75cad593d429c080f378579d12b | |
| parent | 3a48740e898c7586d119bd821572265418ad7b43 (diff) | |
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
| -rw-r--r-- | doc/src/sgml/pgbuffercache.sgml | 11 |
1 files changed, 5 insertions, 6 deletions
diff --git a/doc/src/sgml/pgbuffercache.sgml b/doc/src/sgml/pgbuffercache.sgml index ddf97c88ea4..e9a00a091bf 100644 --- a/doc/src/sgml/pgbuffercache.sgml +++ b/doc/src/sgml/pgbuffercache.sgml @@ -135,12 +135,11 @@ </para> <para> - When the <structname>pg_buffercache</> 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> |