Re: pg_upgrade from pg19 source build to pg19-beta3 throws an error

From: mailinglists <lists(at)database(dot)one>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: pg_upgrade from pg19 source build to pg19-beta3 throws an error
Date: 2026-08-16 19:26:41
Message-ID: D570B259-C763-418F-872D-B014BB727864@database.one
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Ah i see, thanks !

Ellert.

> On 16 Aug 2026, at 19:58, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> mailinglists <lists(at)database(dot)one> writes:
>> Trying an pg_upgrade from pg19 source build (from februari 2026) to pg19-beta3
>
> Yeah, you're outta luck on that one. pg_stats gained a tableid column
> sometime after February, but pg_dump will try to use the column
> anytime the source server reports itself as v19 or newer. There's no
> provision in there for distinguishing different development versions.
>
> I think you can get your data out by using pg_dump or pg_upgrade with
> --no-statistics. In general though, keeping important data in a
> development version is highly not recommended.
>
> regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrey Rachitskiy 2026-08-16 20:08:07 Re: Residual cleanups for tied objects in PL/Perl
Previous Message Tom Lane 2026-08-16 19:04:30 Re: Residual cleanups for tied objects in PL/Perl