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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: mailinglists <lists(at)database(dot)one>
Cc: 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 17:58:28
Message-ID: 570953.1786903108@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2026-08-16 18:04:20 Re: Make tsqueryout() use a StringInfo
Previous Message Tom Lane 2026-08-16 17:38:21 Residual cleanups for tied objects in PL/Perl