Re: postgres.h included from relcache.h - but removing it breaks pg_upgrade - Mailing list pgsql-hackers

From Alexander Korotkov
Subject Re: postgres.h included from relcache.h - but removing it breaks pg_upgrade
Date
Msg-id CAPpHfdst2XnxoQt_rw+ZrFHSyXXTUosE3rhc5+Qcj4OobKG66g@mail.gmail.com
Whole thread Raw
In response to Re: postgres.h included from relcache.h - but removing it breaks pg_upgrade  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Responses Re: postgres.h included from relcache.h - but removing it breaks pg_upgrade  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On Sat, Sep 18, 2021 at 11:35 PM Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
> On 2021-Sep-18, Alexander Korotkov wrote:
>
> > I see now.  I think I'm rather favoring splitting visibilitymap.h.
>
> Agreed, this looks sane to me.  However, I think the
> VM_ALL_{VISIBLE,FROZEN} macros should remain in visibilitymap.h, since
> they depend on the visibilitymap_get_status function (and pg_upgrade
> doesn't use them).
>
> There's a typo "maros" for "macros" in the new header file.  (Also, why
> does the copyright line say "portions" if no portion under another
> copyright?  I think we don't say "portions" when there is only one
> copyright statement line.)

Thank you for the feedback.  All changes are accepted.

Any objections to pushing this?

------
Regards,
Alexander Korotkov

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Undocumented AT TIME ZONE INTERVAL syntax
Next
From: Simon Riggs
Date:
Subject: Re: WIP: System Versioned Temporal Table