diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2025-01-29 13:23:31 -0500 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2025-01-29 13:23:31 -0500 |
| commit | f6ff75f79689d2d0c5bb241435d7fc6a63273223 (patch) | |
| tree | b72038a3359eb8016a422871e0e1eb010ae60a7b /src/tutorial/funcs.source | |
| parent | 128897b101e0a7bc8621abac746ea99d444d83ae (diff) | |
| download | postgresql-f6ff75f79689d2d0c5bb241435d7fc6a63273223.tar.gz postgresql-f6ff75f79689d2d0c5bb241435d7fc6a63273223.zip | |
Make BufferIsExclusiveLocked and BufferIsDirty work for local buffers.
These functions tried to check the state of the buffer's content lock
even for local buffers. Since we don't use the content lock for a
local buffer, that would lead to a "false" result from
LWLockHeldByMeInMode, which would mean a misleading "false" answer
from BufferIsExclusiveLocked (we'd rather that case always return
"true") or an assertion failure in BufferIsDirty.
The core code never applies these two functions to local buffers,
and apparently no extensions do either, since we've not heard
complaints. Still, in the name of future-proofing, let's fix
them to act as though a pinned local buffer is content-locked.
Author: Srinath Reddy <srinath2133@gmail.com>
Discussion: https://postgr.es/m/19396ef77f8.1098c4a1810508.2255483659262451647@zohocorp.com
Diffstat (limited to 'src/tutorial/funcs.source')
0 files changed, 0 insertions, 0 deletions