On Thu, Nov 5, 2020 at 8:17 PM Tom Lane wrote:
>
> Magnus Hagander writes:
> > On Thu, Nov 5, 2020 at 3:50 PM Tom Lane 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 pro
Magnus Hagander writes:
> On Thu, Nov 5, 2020 at 3:50 PM Tom Lane 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 fai
On Thu, Nov 5, 2020 at 3:50 PM Tom Lane wrote:
>
> Peter Eisentraut writes:
> > This commit assigns OIDs from the reserved range:
> > +DECLARE_TOAST(pg_depend, , 8889);
>
> > Do you want to try the renumber_oids.pl script to fix this?
>
> AFAIK the agreed-on process is to do that once per rel
On 2020-11-05 15:50, Tom Lane wrote:
Peter Eisentraut writes:
This commit assigns OIDs from the reserved range:
+DECLARE_TOAST(pg_depend, , 8889);
Do you want to try the renumber_oids.pl script to fix this?
AFAIK the agreed-on process is to do that once per release cycle.
Is there some
Peter Eisentraut writes:
> This commit assigns OIDs from the reserved range:
> +DECLARE_TOAST(pg_depend, , 8889);
> Do you want to try the renumber_oids.pl script to fix this?
AFAIK the agreed-on process is to do that once per release cycle.
Is there some reason why it needs to be done now?
This commit assigns OIDs from the reserved range:
+DECLARE_TOAST(pg_depend, , 8889);
Do you want to try the renumber_oids.pl script to fix this?
On 2020-11-02 13:27, Thomas Munro wrote:
Add pg_depend.refobjversion.
Provide a place for the version of referenced database objects to be
reco
