| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | Christoph Berg <myon(at)debian(dot)org>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Teodor Sigaev <teodor(at)sigaev(dot)ru>, Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> |
| Subject: | Re: BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)« |
| Date: | 2019-07-18 20:57:50 |
| Message-ID: | 20190718205750.GA23460@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 2019-Jul-18, Peter Geoghegan wrote:
> On Thu, Jul 18, 2019 at 2:30 AM Christoph Berg <myon(at)debian(dot)org> wrote:
> > That version works as well on 12 HEAD. It passes "check world" and the
> > Debian testsuite on top of that running 10->12 upgrade tests.
>
> Pushed a slightly refined version of the same patch back to the v11 branch.
Thank you!
I wonder what the consequences are in a system that doesn't have
assertions enabled. Do we just end up with an "upgraded" cached
metapage, and no further ill effects? That seems pretty benign ...
I hope we don't end up with an expected v4 metapage or something crazy
like that? (I suppose we would have noticed.)
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2019-07-18 21:27:45 | Re: BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)« |
| Previous Message | Peter Geoghegan | 2019-07-18 20:25:02 | Re: BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)« |