Re: BUG #19102: Assertion failure in generate_orderedappend_paths with aggregate pushdown

From: Richard Guo <guofenglinux(at)gmail(dot)com>
To: Kuntal Ghosh <kuntalghosh(dot)2007(at)gmail(dot)com>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org, akorotkov(at)postgresql(dot)org
Subject: Re: BUG #19102: Assertion failure in generate_orderedappend_paths with aggregate pushdown
Date: 2025-11-05 01:50:15
Message-ID: CAMbWs4-=rjE4fFYXbpkTWzihQaoJ1pn2geczDiXvVdFWtnubSQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Nov 4, 2025 at 4:44 PM Richard Guo <guofenglinux(at)gmail(dot)com> wrote:
> The assertion failure also exists in v18, so I think it would be best
> to get 0001 pushed and backpatched before the code freeze. I'm not
> sure whether 0002 should be backpatched. Before that, I'd like to
> know whether these two patches make sense.

With the code freeze just a couple of days away, I plan to push and
backpatch v2-0001 shortly, barring any objections.

- Richard

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Kuntal Ghosh 2025-11-05 06:04:11 Re: BUG #19102: Assertion failure in generate_orderedappend_paths with aggregate pushdown
Previous Message Michael Paquier 2025-11-05 01:46:24 Re: BUG #19093: Behavioral change in walreceiver termination between PostgreSQL 14.17 and 14.18