Re: generate syscache info automatically - Mailing list pgsql-hackers

From John Naylor
Subject Re: generate syscache info automatically
Date
Msg-id CANWCAZbvK_OVAfZPXxK8tey53CTnmwuxgJAbFEBWt57rAUN0Ag@mail.gmail.com
Whole thread Raw
In response to Re: generate syscache info automatically  (Peter Eisentraut <peter@eisentraut.org>)
Responses Re: generate syscache info automatically  (Peter Eisentraut <peter@eisentraut.org>)
List pgsql-hackers
On Wed, Jan 17, 2024 at 7:46 PM Peter Eisentraut <peter@eisentraut.org> wrote:
>
> I updated the patch to use this style (but I swapped the first two
> arguments from my example, so that the thing being created is named first).
>
> I also changed the names of the output files a bit to make them less
> confusing.  (I initially had some files named .c.h, which was weird, but
> apparently necessary to avoid confusing the build system.  But it's all
> clearer now.)
>
> Other than bugs and perhaps style opinions, I think the first patch is
> pretty good now.

LGTM. The only style consideration that occurred to me just now was
MAKE_SYSCACHE, since it doesn't match the DECLARE_... macros. It seems
like the same thing from a code generation perspective. The other
macros refer to relations, so there is a difference, but maybe it
doesn't matter. I don't have a strong opinion.



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: "ERROR: could not open relation with OID 16391" error was encountered when reindexing
Next
From: Amit Kapila
Date:
Subject: Re: Synchronizing slots from primary to standby