summaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2025-11-28 08:00:23 +0900
committerMichael Paquier <michael@paquier.xyz>2025-11-28 08:00:23 +0900
commitc75bf57a90e05bf35afa00e66986b9210833bdaf (patch)
tree005b965ad45903a03c2883ec6ec1cbd0c7d281ee /doc/src
parent9660906dbd696146da2c1d8bfdce26b1a2bed1c3 (diff)
doc: Add missing tags in pg_buffercache page
Issue noticed while looking at this area of the documentation, for a different patch. This is a matter of style, so no backpatch is done. Discussion: https://postgr.es/m/CAN55FZ0h_YoSqqutxV6DES1RW8ig6wcA8CR9rJk358YRMxZFmw@mail.gmail.com
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/pgbuffercache.sgml6
1 files changed, 4 insertions, 2 deletions
diff --git a/doc/src/sgml/pgbuffercache.sgml b/doc/src/sgml/pgbuffercache.sgml
index 91bbedff343..a011c749c8a 100644
--- a/doc/src/sgml/pgbuffercache.sgml
+++ b/doc/src/sgml/pgbuffercache.sgml
@@ -536,10 +536,12 @@
The <function>pg_buffercache_evict()</function> function takes a buffer
identifier, as shown in the <structfield>bufferid</structfield> column of
the <structname>pg_buffercache</structname> view. It returns information
- about whether the buffer was evicted and flushed. The buffer_evicted
+ about whether the buffer was evicted and flushed.
+ The <structfield>buffer_evicted</structfield>
column is true on success, and false if the buffer wasn't valid, if it
couldn't be evicted because it was pinned, or if it became dirty again
- after an attempt to write it out. The buffer_flushed column is true if the
+ after an attempt to write it out.
+ The <structfield>buffer_flushed</structfield> column is true if the
buffer was flushed. This does not necessarily mean that buffer was flushed
by us, it might be flushed by someone else. The result is immediately out
of date upon return, as the buffer might become valid again at any time due