Re: ERROR: corrupt MVNDistinct entry - Mailing list pgsql-hackers

From Richard Guo
Subject Re: ERROR: corrupt MVNDistinct entry
Date
Msg-id CAMbWs4-evCAvjm9bqu_MHHjNj_nE8ZWHfpuh9m7u346C2dTw-w@mail.gmail.com
Whole thread Raw
In response to ERROR: corrupt MVNDistinct entry  (Richard Guo <guofenglinux@gmail.com>)
List pgsql-hackers
On Tue, Dec 31, 2024 at 5:40 PM Richard Guo <guofenglinux@gmail.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



pgsql-hackers by date:

Previous
From: vignesh C
Date:
Subject: Re: Conflict detection for update_deleted in logical replication
Next
From: Ashutosh Bapat
Date:
Subject: Re: apply_scanjoin_target_to_paths and partitionwise join