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

Поиск
Список
Период
Сортировка
От Peter Geoghegan
Тема Re: BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)«
Дата
Msg-id CAH2-WznYXDG6aANoag5ixoMrV=0bD-W5i9cVq4cRkb-fA4xRmw@mail.gmail.com
обсуждение исходный текст
Ответ на BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)«  (PG Bug reporting form <noreply@postgresql.org>)
Ответы Re: BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)«  (Christoph Berg <myon@debian.org>)
Список pgsql-bugs
Дерево обсуждения 
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 по дате отправления:

Предыдущее
От: Manuel Rigger
Дата:
Сообщение: Re: VACUUM FULL results in deadlock
Следующее
От: Tom Lane
Дата:
Сообщение: Re: ALTER TABLE SET WITH OIDS fails after failed CONCURRENTLY index creation