Re: How to REMOVE a fillfactor set by accident?

Поиск
Список
Период
Сортировка
От David G. Johnston
Тема Re: How to REMOVE a fillfactor set by accident?
Дата
Msg-id CAKFQuwaPQu-ssBd9OU_vZXDqFsMAc=T1G1DuVjnEFmp9kLrCqQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: How to REMOVE a fillfactor set by accident?  (Ron <ronljohnsonjr@gmail.com>)
Список pgsql-general
On Thu, Dec 31, 2020 at 1:24 PM Ron <ronljohnsonjr@gmail.com> wrote:
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%.


Since the index already exists the "ALTER INDEX" documentation is more pertinent.  And behold:

ALTER INDEX [ IF EXISTS ] name RESET ( storage_parameter [, ... ] )

David J.

В списке pgsql-general по дате отправления:

Предыдущее
От: Thomas Kellerer
Дата:
Сообщение: Re: How to REMOVE a fillfactor set by accident?
Следующее
От: Michael Lewis
Дата:
Сообщение: Re: Declarative partitioning and automatically generated row-IDs using BIGSERIAL