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

From: Bernd Helmle <mailings(at)oopsware(dot)de>
To: myon(at)debian(dot)org, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)«
Date: 2019-07-05 12:51:01
Message-ID: 7a57028cce96362a4c1451a50227c323ac8a8b52.camel@oopsware.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Am Freitag, den 05.07.2019, 09:59 +0000 schrieb PG Bug reporting form:
> 12beta2:
> SELECT * FROM phone ORDER BY name;
> TRAP: FailedAssertion(»!(metad->btm_version >= 3)«, Datei:
> »/build/postgresql-12-3URvLF/postgresql-12-
> 12~beta2/build/../src/backend/access/nbtree/nbtpage.c«,
> Zeile: 665)
> 2019-07-05 11:34:35.040 CEST [14325] LOG: Serverprozess (PID 14376)
> wurde
> von Signal 6 beendet: Abgebrochen
> 2019-07-05 11:34:35.040 CEST [14325] DETAIL: Der fehlgeschlagene
> Prozess
> führte aus: SELECT * FROM phone ORDER BY name;

Additional note from me after a short test:

It works if you upgrade to PG11 first _and_ have touched the index in a
way it has rewritten the metapage to version 3, e.g. adding new pages
to the index.

Thanks

Bernd

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Robert Haas 2019-07-05 13:08:33 Re: BUG #15895: pg_dump execution with OpenSSL encryption from Windows Service application
Previous Message PG Bug reporting form 2019-07-05 11:10:32 BUG #15897: make failed postgres 11.4 at 32 bit build