Re: Fix for pageinspect bug in PG 17

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Tomas Vondra <tomas(at)vondra(dot)me>
Cc: "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Fix for pageinspect bug in PG 17
Date: 2024-11-14 00:55:52
Message-ID: CAH2-WzmCc9Q1CHzFPfB1QESJbi2pOtD90xODt=zBXJaAYxvqvg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Nov 13, 2024 at 3:00 PM Tomas Vondra <tomas(at)vondra(dot)me> wrote:
> Does that mean you think we should fix the issue at hand differently?
> Say, by looking at number of columns and building the correct tuple,
> like I did in my initial patch?

I don't feel strongly about it either way. But if it was my fix I'd
probably make it work on both versions. There's plenty of precedent
for that.

--
Peter Geoghegan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Richard Guo 2024-11-14 01:09:32 Re: Reordering DISTINCT keys to match input path's pathkeys
Previous Message Peter Geoghegan 2024-11-14 00:54:03 Re: Fix for pageinspect bug in PG 17