Re: A strange GiST error message or fillfactor of GiST build

From: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
To: Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: A strange GiST error message or fillfactor of GiST build
Date: 2018-08-30 12:39:21
Message-ID: 9FDF5560-2104-48F5-B671-7399651B7FA4@yandex-team.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello!

> 30 авг. 2018 г., в 2:42, Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> написал(а):
>
> At Wed, 29 Aug 2018 10:42:59 -0300, Andrey Borodin <x4mmm(at)yandex-team(dot)ru> wrote in <6FBE12B2-4F59-4DB9-BDE9-62C8801189A8(at)yandex-team(dot)ru>
>>
>> We are passing freespace everywhere. Also, we pass GistInsertState, and GistState.
>> Maybe let's put GistState into GistInsertState, GistState already has free space, and pass just GistInsertState everywhere?
>
> Yeah, I thought something like that first. GISTSTATE doesn't have
> freespace size but we could refactor so that all insert-related
> routines use GISTInsertState and make GISTBuildState have
> it. (patch 1) But this prevents future back-patching so I don't
> think this acceptable.

The patch looks good to me. Making code better for future development seem to me more important than backpatching this: error per se is cryptic but not threatening, it will be prevented by cube construction routines limitations.
But that is just my IMHO.

Best regards, Andrey Borodin.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Erik Rijkers 2018-08-30 12:51:45 Re: rare crash - FailedAssertion snapbuild.c Line: 580
Previous Message Andrew Gierth 2018-08-30 11:49:46 Re: Catalog corruption