Re: pg_upgrade (12->14) fails on aggregate

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Petr Vejsada <pve(at)paymorrow(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: pg_upgrade (12->14) fails on aggregate
Date: 2022-07-07 05:04:13
Message-ID: YsZpTczXmzlJa3//@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On Tue, Jul 05, 2022 at 11:29:03PM -0400, Tom Lane wrote:
> Yeah. I think that 08385ed26 fixes this, but we've had no new
> reports yet :-(

Indeed. Things are right now. Thanks!
--
Michael

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2022-07-07 18:02:24 Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower
Previous Message Andres Freund 2022-07-07 04:36:56 Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2022-07-07 05:45:23 Re: Eliminating SPI from RI triggers - take 2
Previous Message Michael Paquier 2022-07-07 04:56:39 Re: Bump MIN_WINNT to 0x0600 (Vista) as minimal runtime in 16~