Postgres Pro
Downloads
Home   >   mailing lists

Re: BUG #16045: vacuum_db crash and illegal memory alloc afterpg_upgrade from PG11 to PG12 - Mailing list pgsql-bugs

From Andres Freund
Subject Re: BUG #16045: vacuum_db crash and illegal memory alloc afterpg_upgrade from PG11 to PG12
Date
Msg-id 20191010014813.3b2btmkakhrskwgd@alap3.anarazel.de
Whole thread Raw
In response to Re: BUG #16045: vacuum_db crash and illegal memory alloc after pg_upgrade from PG11 to PG12  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #16045: vacuum_db crash and illegal memory alloc afterpg_upgrade from PG11 to PG12
List pgsql-bugs
Tree view 
On 2019-10-09 19:41:54 -0400, Tom Lane wrote:
> Also, even if we did try to silently convert such columns that way,
> I bet we'd get other bug reports about "why'd my columns suddenly
> change type?".  So I'd rather force the user to be involved.

+1

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #16045: vacuum_db crash and illegal memory alloc after pg_upgrade from PG11 to PG12
Next
From: Andres Freund
Date:
Subject: Re: BUG #16038: Alter table - SegFault