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

From: Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>
To: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
Cc: a(dot)korotkov(at)postgrespro(dot)ru, tgl(at)sss(dot)pgh(dot)pa(dot)us, robertmhaas(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: A strange GiST error message or fillfactor of GiST build
Date: 2018-09-06 07:16:45
Message-ID: 17147719-563b-2ae9-3970-0bb73eaf181f@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello.

> Just my 2 cents: that was a hacky use case for development reasons.

I know. So I intended to preserve the parameter with default of 100% if
no one strongly objects to preserve. Then I abandoned that since I had:p

> I think that removing fillfactor is good idea and your latest patch
> looks good from my POV.

Thanks.

reagrds.

--
Kyotaro Horiguchi
NTT Open Source Software Center

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kyotaro HORIGUCHI 2018-09-06 08:00:13 Re: Reopen logfile on SIGHUP
Previous Message Kyotaro HORIGUCHI 2018-09-06 07:10:03 Re: [HACKERS] Restricting maximum keep segments by repslots