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

From Alvaro Herrera
Subject Re: postgres.h included from relcache.h - but removing it breaks pg_upgrade
Date
Msg-id 202109182035.ls55i32hwvta@alvherre.pgsql
Whole thread Raw
In response to Re: postgres.h included from relcache.h - but removing it breaks pg_upgrade  (Alexander Korotkov <aekorotkov@gmail.com>)
Responses Re: postgres.h included from relcache.h - but removing it breaks pg_upgrade
List pgsql-hackers
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.)

-- 
Álvaro Herrera              Valdivia, Chile  —  https://www.EnterpriseDB.com/



pgsql-hackers by date:

Previous
From: Alexander Korotkov
Date:
Subject: Re: postgres.h included from relcache.h - but removing it breaks pg_upgrade
Next
From: Justin Pryzby
Date:
Subject: Re: PG 14 release notes, first draft