Re: fillfactor gets set to zero for toast tables - Mailing list pgsql-hackers

From Tom Lane
Subject Re: fillfactor gets set to zero for toast tables
Date
Msg-id 20795.1273863837@sss.pgh.pa.us
Whole thread Raw
In response to Re: fillfactor gets set to zero for toast tables  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: fillfactor gets set to zero for toast tables
List pgsql-hackers
Alvaro Herrera <alvherre@commandprompt.com> writes:
> Excerpts from Tom Lane's message of vie may 14 14:19:30 -0400 2010:
>> What seems more rational is to provide toast.fillfactor but give it
>> min/max/default = 100.

> Adding an entry to intRelOpts should be enough to fix this bug, correct?

I think so, but haven't tested.  The docs would need some correction
perhaps.

BTW, I notice that the code allows people to fool with
autovacuum_analyze_threshold and related parameters for toast tables,
which seems rather pointless since we never analyze toast tables.
So the fillfactor isn't really the only instance of the issue.

Maybe a better solution is to have some kind of notion of a default-only
entry, which is sufficient to insert the default into the struct but
isn't accepted as a user-settable item.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Peter Crabtree
Date:
Subject: Generating Lots of PKs with nextval(): A Feature Proposal
Next
From: Kenneth Marshall
Date:
Subject: Re: Generating Lots of PKs with nextval(): A Feature Proposal