Peter Eisentraut <peter@eisentraut.org> writes:
> In these cases, I think for
> NotificationHash
> ResourceOwnerData
> WalSyncMethod
> we can just get rid of the typedef.
I have no objection to dealing with NotificationHash as you have here.
> ReadBuffersFlags shouldn't be an enum at all, because its values are
> used as flag bits.
Yeah, that was bothering me too, but I went for the minimum delta.
I did think that a couple of integer macros would be a better idea,
so +1 for what you did here.
> WaitEventExtension, I'm not sure, it's like, an extensible enum? I
> guess let's remove the typedef there, too.
I am also quite confused by that. It seems to be kind of an enum
that is supposed to be extended at runtime, meaning that neither
of the existing enum member values ought to be used as such, although
either autoprewarm.c didn't get the memo or I misunderstand the
intended usage. NUM_BUILTIN_WAIT_EVENT_EXTENSION is possibly the
most bizarre idea I've ever seen: what would a "built-in extension"
event be exactly? I think the enum should be nuked altogether, but
it's a bit late to be redesigning that for v17 perhaps.
> Attached is a variant patch.
I'm good with this, with a mental note to look again at
WaitEventExtension later.
regards, tom lane
