| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> |
| Cc: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, 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-07 19:09:37 |
| Message-ID: | 20180907190937.GD28811@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Sep 6, 2018 at 04:16:45PM +0900, Kyotaro HORIGUCHI wrote:
> 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
So, are we going to output a notice if a non-100% fill factor is
specified?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2018-09-07 19:48:29 | Re: pg_constraint.conincluding is useless |
| Previous Message | Alexander Kuzmenkov | 2018-09-07 18:53:27 | Re: Performance improvements for src/port/snprintf.c |