mirror of
				https://github.com/postgres/postgres.git
				synced 2025-11-03 09:13:20 +03: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:
		@@ -135,12 +135,11 @@
 | 
				
			|||||||
  </para>
 | 
					  </para>
 | 
				
			||||||
 | 
					
 | 
				
			||||||
  <para>
 | 
					  <para>
 | 
				
			||||||
   When the <structname>pg_buffercache</> view is accessed, internal buffer
 | 
					   Since buffer manager locks are not taken to copy the buffer state data that
 | 
				
			||||||
   manager locks are taken for long enough to copy all the buffer state
 | 
					   the view will display, accessing <structname>pg_buffercache</structname> view
 | 
				
			||||||
   data that the view will display.
 | 
					   has less impact on normal buffer activity but it doesn't provide a consistent
 | 
				
			||||||
   This ensures that the view produces a consistent set of results, while not
 | 
					   set of results across all buffers.  However, we ensure that the information of
 | 
				
			||||||
   blocking normal buffer activity longer than necessary.  Nonetheless there
 | 
					   each buffer is self-consistent.
 | 
				
			||||||
   could be some impact on database performance if this view is read often.
 | 
					 | 
				
			||||||
  </para>
 | 
					  </para>
 | 
				
			||||||
 </sect2>
 | 
					 </sect2>
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 
 | 
				
			|||||||
		Reference in New Issue
	
	Block a user