Re: SP-GiST confusion: indexed column's type vs. index column type - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: SP-GiST confusion: indexed column's type vs. index column type
Date
Msg-id CAH2-WzkU7RX1Zb+bj1aH577bb20eGex2W9DmPzDBritxGqcUCQ@mail.gmail.com
Whole thread Raw
In response to SP-GiST confusion: indexed column's type vs. index column type  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: SP-GiST confusion: indexed column's type vs. index column type  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Fri, Apr 2, 2021 at 9:37 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> I propose changing things so that
>
> (A) attType really is the input (heap) data type.
>
> (B) We enforce that leafType agrees with the opclass opckeytype,
> ensuring the index tupdesc can be used for leaf tuples.
>
> (C) The tupdesc passed back for an index-only scan reports the
> input (heap) data type.
>
> This might be too much change for the back branches.  Given the
> lack of complaints to date, I think we can just fix it in HEAD.

+1 to fixing it on HEAD only.

-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: SP-GiST confusion: indexed column's type vs. index column type
Next
From: Andres Freund
Date:
Subject: Re: Process initialization labyrinth