| From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
|---|---|
| To: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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-15 04:41:18 |
| Message-ID: | 20191015044118.GO3599@telsasoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
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.
Perhaps it'd be worth creating a test for on-disk format ?
Like a table with a column for each core type, which is either SELECTed from
after pg_upgrade, or pg_dump output compared before and after.
Justin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2019-10-15 07:07:25 | Re: BUG #16045: vacuum_db crash and illegal memory alloc after pg_upgrade from PG11 to PG12 |
| Previous Message | Jeff Janes | 2019-10-15 00:35:16 | Re: BUG #16054: Slowest individual queries |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2019-10-15 05:03:54 | Re: [HACKERS] Block level parallel vacuum |
| Previous Message | Thomas Munro | 2019-10-15 04:39:16 | Re: Collation versioning |