Re: pgsql: Add pg_depend.refobjversion.

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Thomas Munro <tmunro(at)postgresql(dot)org>, pgsql-committers <pgsql-committers(at)lists(dot)postgresql(dot)org>
Subject: Re: pgsql: Add pg_depend.refobjversion.
Date: 2020-11-05 19:25:45
Message-ID: CABUevEy7JmBcCbVk5CFBOdaK6gX-eC2VtBFSQ9Tpn+bNLvTyOw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Thu, Nov 5, 2020 at 8:17 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Magnus Hagander <magnus(at)hagander(dot)net> writes:
> > On Thu, Nov 5, 2020 at 3:50 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> >> AFAIK the agreed-on process is to do that once per release cycle.
> >> Is there some reason why it needs to be done now?
>
> > Did we ever actually document this process somewhere? I went looking
> > for it some time ago and failed to find it (and eventually found the
> > old email thread(s) around it, but that's not really documentation),
> > but that could definitely be my searching....
>
> Yeah, it's documented here:
>
> https://www.postgresql.org/docs/devel/system-catalog-initial-data.html#SYSTEM-CATALOG-OID-ASSIGNMENT
>
> and there is an entry in src/tools/RELEASE_CHANGES to remind us
> to actually do the cleanup work.

Ha! Thanks.

I did find the RELEASE_CHANGES ones, but for some reason managed to
miss the other one.

--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Geoghegan 2020-11-05 23:02:35 pgsql: Fix wal_consistency_checking nbtree bug.
Previous Message Tom Lane 2020-11-05 19:17:57 Re: pgsql: Add pg_depend.refobjversion.