Re: [HACKERS] Allow GiST opcalsses without compress\decompresfunctions - Mailing list pgsql-hackers

From Andrey Borodin
Subject Re: [HACKERS] Allow GiST opcalsses without compress\decompresfunctions
Date
Msg-id 0FB0A1B4-919B-43D8-8F55-EA69772064B1@yandex-team.ru
Whole thread Raw
In response to Re: [HACKERS] Allow GiST opcalsses without compress\decompres functions  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [HACKERS] Allow GiST opcalsses without compress\decompres functions
Re: [HACKERS] Allow GiST opcalsses without compress\decompres functions
List pgsql-hackers
Hello Tom! Thanks for committing the patch!

> 20 сент. 2017 г., в 8:38, Tom Lane <tgl@sss.pgh.pa.us> написал(а):
>
> Andrey Borodin <x4mmm@yandex-team.ru> writes:
>> [ 0001-Allow-uncompressed-GiST-4.patch ]
>
> ... There's still room
> to improve the contrib opclasses

I have one important question regarding compress\decompres functions.

You mentioned that probably there cannot be TOASTed values in the index.
I need to settle this question in more deterministic way.
Can you point where to look at the code or who to ask:
Can there be TOASTed values in index tuples?

If answer is NO, we can get rid of much more useless code.

Best regards, Andrey Borodin.

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

pgsql-hackers by date:

Previous
From: Ashutosh Sharma
Date:
Subject: Re: [HACKERS] Page Scan Mode in Hash Index
Next
From: Ashutosh Bapat
Date:
Subject: Re: [HACKERS] Partition-wise join for join between (declaratively)partitioned tables