Re: BUG #16045: vacuum_db crash and illegal memory alloc after pg_upgrade from PG11 to PG12

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, buschmann(at)nidsa(dot)net, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #16045: vacuum_db crash and illegal memory alloc after pg_upgrade from PG11 to PG12
Date: 2019-10-16 12:27:57
Message-ID: 11353.1571228877@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> writes:
> I've just committed and pushed both fixes after some minor corrections.

Not quite right in 9.6 and before, according to crake. Looks like
some issue with the CppAsString2'd constants? Did we even have
CppAsString2 that far back?

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2019-10-16 13:26:42 Re: BUG #16045: vacuum_db crash and illegal memory alloc after pg_upgrade from PG11 to PG12
Previous Message death lock 2019-10-16 11:42:20 Re: BUG #16049: log_line_prefix=%a and log_connections - application_name missing

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2019-10-16 12:32:48 Re: configure fails for perl check on CentOS8
Previous Message Masahiko Sawada 2019-10-16 12:04:40 Re: maintenance_work_mem used by Vacuum