Re: Allow GiST opcalsses without compress\decompres functions

From: Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, Dmitriy Sarafannikov <dsarafannikov(at)yandex(dot)ru>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Allow GiST opcalsses without compress\decompres functions
Date: 2017-09-20 14:09:38
Views: Raw Message | Whole Thread | Download mbox
Lists: pgsql-hackers

On Wed, Sep 20, 2017 at 5:02 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> writes:
> > On Wed, Sep 20, 2017 at 4:25 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> >> Yes. We don't allow out-of-line values, but we do allow compressed and
> >> short-header values.
> > BTW, this comment looks still invalid for me...
> >> #define SIGLENINT 4 /* >122 => key will *toast*, so very slow!!! */
> I haven't done the math to see if 122 is exactly the right value,
> but at some point index_form_tuple would decide that the tuple was
> uncomfortably big and try to compress it. So the comment is right
> in general terms.

If comment means toast as compression, not out-of-line storage then it's
However, it would be good to rephrase this comment to clarify that.

Alexander Korotkov
Postgres Professional:
The Russian Postgres Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2017-09-20 14:21:53 Re: Re: [COMMITTERS] pgsql: Expand partitioned table RTEs level by level, without flattening
Previous Message Robert Haas 2017-09-20 14:06:26 Re: SCRAM in the PG 10 release notes