Postgres Pro
Downloads
Home   >   mailing lists

Re: BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)« - Mailing list pgsql-bugs

From Peter Geoghegan
Subject Re: BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)«
Date
Msg-id CAH2-WznYXDG6aANoag5ixoMrV=0bD-W5i9cVq4cRkb-fA4xRmw@mail.gmail.com
Whole thread Raw
In response to BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)«  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)«  (Christoph Berg <myon@debian.org>)
List pgsql-bugs
Tree view 
On Fri, Jul 5, 2019 at 3:00 AM PG Bug reporting form
<noreply@postgresql.org> wrote:
> When pg_upgrading from 10-or-earlier to 12beta2 or 13devel, an assertion is
> raised. (Spotted by Debian's postgresql-common upgrade tests. Previously
> missed because we were only testing version+1 upgrades.)

Obviously you were right to adopt pg_upgrade tests that cross more
than one version at a time. Thanks!

-- 
Peter Geoghegan

pgsql-bugs by date:

Previous
From: Manuel Rigger
Date:
Subject: Re: VACUUM FULL results in deadlock
Next
From: Tom Lane
Date:
Subject: Re: ALTER TABLE SET WITH OIDS fails after failed CONCURRENTLY index creation