Re: BUG #16045: vacuum_db crash and illegal memory alloc afterpg_upgrade from PG11 to PG12
От | Tomas Vondra |
---|---|
Тема | Re: BUG #16045: vacuum_db crash and illegal memory alloc afterpg_upgrade from PG11 to PG12 |
Дата | |
Msg-id | 20191016113344.ihrjpztakfppgilp@development обсуждение исходный текст |
Ответ на | Re: BUG #16045: vacuum_db crash and illegal memory alloc afterpg_upgrade from PG11 to PG12 (Tomas Vondra <tomas.vondra@2ndquadrant.com>) |
Ответы |
Re: BUG #16045: vacuum_db crash and illegal memory alloc after pg_upgrade from PG11 to PG12
|
Список | pgsql-bugs |
On Tue, Oct 15, 2019 at 02:18:17AM +0200, Tomas Vondra wrote: >On Mon, Oct 14, 2019 at 06:35:38PM +0200, Tomas Vondra wrote: >>... >> >>Aha! I forgot we copy the necessary stuff into pg_attribute. Thanks for >>clarifying, I'll polish and push the fix shortly. >> > >I've pushed and backpatched the fix. Attached are similar fixes for the >existing pg_upgrade checks for pg_catalog.line and pg_catalog.unknown >types, which have the same issues with composite types and domains. > >There are some additional details & examples in the commit messages. > >I've kept this in two patches primarily because of backpatching - the >line fix should go back up to 9.4, the unknown is for 10. > I've just committed and pushed both fixes after some minor corrections. regards -- Tomas Vondra http://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-bugs по дате отправления: