mirror of
https://github.com/postgres/postgres.git
synced 2025-12-09 02:08:45 +03:00
Rename BUFFERPIN wait event class to BUFFER
In an upcoming patch more wait events will be added to the wait event class (for buffer locking), making the current name too specific. Alternatively we could introduce a dedicated wait event class for those, but it seems somewhat confusing to have a BUFFERPIN and a BUFFER wait event class. Reviewed-by: Melanie Plageman <melanieplageman@gmail.com> Discussion: https://postgr.es/m/fvfmkr5kk4nyex56ejgxj3uzi63isfxovp2biecb4bspbjrze7@az2pljabhnff
This commit is contained in:
@@ -1053,11 +1053,9 @@ postgres 27093 0.0 0.0 30096 2752 ? Ss 11:34 0:00 postgres: ser
|
||||
</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry><literal>BufferPin</literal></entry>
|
||||
<entry>The server process is waiting for exclusive access to
|
||||
a data buffer. Buffer pin waits can be protracted if
|
||||
another process holds an open cursor that last read data from the
|
||||
buffer in question. See <xref linkend="wait-event-bufferpin-table"/>.
|
||||
<entry><literal>Buffer</literal></entry>
|
||||
<entry>The server process is waiting for access to a data buffer.
|
||||
See <xref linkend="wait-event-buffer-table"/>.
|
||||
</entry>
|
||||
</row>
|
||||
<row>
|
||||
|
||||
Reference in New Issue
Block a user