Re: ERROR: corrupt MVNDistinct entry

From: Richard Guo <guofenglinux(at)gmail(dot)com>
To: Andrei Lepikhov <lepihov(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ERROR: corrupt MVNDistinct entry
Date: 2025-01-02 09:30:04
Message-ID: CAMbWs4-evCAvjm9bqu_MHHjNj_nE8ZWHfpuh9m7u346C2dTw-w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Dec 31, 2024 at 5:40 PM Richard Guo <guofenglinux(at)gmail(dot)com> wrote:
> Regarding the back-patch, this patch is a bug fix, which suggests it
> should be back-patched. However, it also changes some plans by fixing
> the cost estimation. Does anyone know what our usual approach is in
> this situation?

Although this patch could result in plan changes, it fixes an actual
bug, so I've back-patched it to v16.

Thanks
Richard

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ashutosh Bapat 2025-01-02 09:41:33 Re: apply_scanjoin_target_to_paths and partitionwise join
Previous Message vignesh C 2025-01-02 09:27:17 Re: Conflict detection for update_deleted in logical replication