From c75bf57a90e05bf35afa00e66986b9210833bdaf Mon Sep 17 00:00:00 2001 From: Michael Paquier Date: Fri, 28 Nov 2025 08:00:23 +0900 Subject: [PATCH] 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 --- doc/src/sgml/pgbuffercache.sgml | 6 ++++-- 1 file 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 pg_buffercache_evict() function takes a buffer identifier, as shown in the bufferid column of the pg_buffercache view. It returns information - about whether the buffer was evicted and flushed. The buffer_evicted + about whether the buffer was evicted and flushed. + The buffer_evicted 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 buffer_flushed 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 -- 2.39.5