Re: pgsql: Move SQL-callable code related to multixacts into its own file - Mailing list pgsql-committers

From Michael Paquier
Subject Re: pgsql: Move SQL-callable code related to multixacts into its own file
Date
Msg-id aKWDGckk3K2ftiPw@paquier.xyz
Whole thread Raw
In response to Re: pgsql: Move SQL-callable code related to multixacts into its own file  (Álvaro Herrera <alvherre@kurilemu.de>)
List pgsql-committers
On Tue, Aug 19, 2025 at 12:31:14PM +0200, Alvaro Herrera wrote:
> Hmm, don't you find strange that dbcommands.h is still included there?
> I wondered about that and found out that we have get_database_name()
> declared there.  It sort-of makes sense, because it was originally done
> by scanning pg_database, but since commit cb98e6fb8fd4 introduced a
> syscache for it, we can have this routine in lsyscache.c/h instead,
> where it feels more at home.  It also seems more sensible to declare
> get_database_oid() in pg_database.h.  After these two changes, a lot of
> files can stop including dbcommands.h.  This seems a nice cleanup to me,
> and passes headerscheck.
>
>  33 files changed, 39 insertions(+), 56 deletions(-)

Indeed, that's a nice located cleanup.
--
Michael

Attachment

pgsql-committers by date:

Previous
From: Michael Paquier
Date:
Subject: pgsql: Fix assertion failure with replication slot release in single-us
Next
From: Tom Lane
Date:
Subject: Re: pgsql: Move SQL-callable code related to multixacts into its own file