From: | Ron <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: How to REMOVE a fillfactor set by accident? |
Date: | 2020-12-31 20:24:00 |
Message-ID: | 426b90ed-d8f7-5a5c-36fb-78c392e8c0d8@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 12/31/20 2:13 PM, Thorsten Schöning wrote:
> Hi all,
>
> I'm using the GUI tool pgModeler to maintain schemas and at some point
> in the past it used fillfactor 10 for some indexes by default. That
> seems to have changed in the meantime and most of my indexes don't
> have ANY fillfactor set explicitly.
>
> Is there some way to REMOVE the fillfactor where it is set, so that
> Postgres applies it's defaults? Would be great to have an output of
> NULL everywhere where fillfactor is output instead of sometimes e.g.
> 100 and more often NULL.
>
> I've already tried setting things to NULL, which failed with
> mentioning that a decimal number is necessary. Though, even setting 0
> fails, because a value between 10 and 100 is required.
>
>> ALTER INDEX pk_clt_rec_src SET (fillfactor = NULL);
>> ALTER INDEX pk_clt_rec_src SET (fillfactor = 0);
> So removing isn't possible at all and I can only set to concrete
> values like 100 or don't care at all instead? Because fillfactor=10 is
> only set for some low throughput test databases currently.
https://www.postgresql.org/docs/12/sql-createindex.html
There *must* be a fill factor; that's how B-tree, hash, GiST and SP-GiST
indices work.
The default fill factor is 90%; thus, to "remove" your custom fill factor,
set it to 90%.
--
Angular momentum makes the world go 'round.
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Kellerer | 2020-12-31 20:31:56 | Re: How to REMOVE a fillfactor set by accident? |
Previous Message | Thorsten Schöning | 2020-12-31 20:13:28 | How to REMOVE a fillfactor set by accident? |