| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | pgsql: bufmgr: Introduce FlushUnlockedBuffer |
| Date: | 2025-10-08 19:46:35 |
| Message-ID: | E1v6a7P-000iyb-11@gemulon.postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
bufmgr: Introduce FlushUnlockedBuffer
There were several copies of code locking a buffer, flushing its contents, and
unlocking the buffer. It seems worth centralizing that into a helper function.
Reviewed-by: Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>
Discussion: https://postgr.es/m/fvfmkr5kk4nyex56ejgxj3uzi63isfxovp2biecb4bspbjrze7@az2pljabhnff
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/3c2b97b29ee33d5619779fd10e06eee07d4700da
Modified Files
--------------
src/backend/storage/buffer/bufmgr.c | 36 ++++++++++++++++++++----------------
1 file changed, 20 insertions(+), 16 deletions(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2025-10-08 20:44:29 | pgsql: bufmgr: fewer calls to BufferDescriptorGetContentLock |
| Previous Message | Andres Freund | 2025-10-08 17:15:10 | pgsql: Improve ReadRecentBuffer() scalability |