1
0
mirror of https://github.com/postgres/postgres.git synced 2025-11-29 23:43:17 +03:00

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
This commit is contained in:
Michael Paquier
2025-11-28 08:00:23 +09:00
parent 9660906dbd
commit c75bf57a90

View File

@@ -536,10 +536,12 @@
The <function>pg_buffercache_evict()</function> function takes a buffer The <function>pg_buffercache_evict()</function> function takes a buffer
identifier, as shown in the <structfield>bufferid</structfield> column of identifier, as shown in the <structfield>bufferid</structfield> column of
the <structname>pg_buffercache</structname> view. It returns information 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 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 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 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 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 of date upon return, as the buffer might become valid again at any time due