Re: BufmgrCommit no-op since 2008, remaining uses?
Matthias van de Meent <boekewurm+postgres@gmail.com>
From: Matthias van de Meent <boekewurm+postgres@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>,
Heikki Linnakangas <hlinnaka@iki.fi>
Date: 2023-03-29T12:49:18Z
Lists: pgsql-hackers
Attachments
- 0001-Cleanup-Drop-BufmgrCommit.patch (application/octet-stream) patch 0001
On Wed, 29 Mar 2023 at 14:12, Tom Lane <tgl@sss.pgh.pa.us> wrote: > > Matthias van de Meent <boekewurm+postgres@gmail.com> writes: > > BufmgrCommit does exactly nothing; it is an empty function and has > > been since commit 33960006 in late 2008 when it stopped calling > > smgrcommit(). > > All two usages of the function (in our code base) seem to be in > > xact.c. Are we maintaining it for potential future use, or can the > > function be removed? > > Seems reasonable. Even if bufmgr grew a new need to be called > during commit, it would quite possibly need to be called from > a different spot; so I doubt that the function is useful even > as a placeholder. Then, the attached trivial patch removes the function and all references I could find. Kind regards, Matthias van de Meent
Commits
-
Remove empty function BufmgrCommit().
- 58c9600a9f58 16.0 landed
-
Rethink the way FSM truncation works. Instead of WAL-logging FSM
- 3396000684b4 8.4.0 cited