On Thu, Nov 12, 2015 at 9:06 AM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Michael Paquier <michael.paqu...@gmail.com> writes: >> On Thu, Nov 12, 2015 at 6:27 AM, Alvaro Herrera >> <alvhe...@2ndquadrant.com> wrote: >>> I think you're remembering this: >>> http://www.postgresql.org/message-id/20150402205713.gb22...@eldon.alvh.no-ip.org > >> Right. Thanks. Do you think we'd still want a patch to improve that? > > Give it a try if you like, and see whether it seems to improve matters. > I did not try moving material around like that in the patch I committed > earlier today.
Hm. I am not sure we are quite at the point of hacking something. The pinpoint regarding such a change would be where to gather a description of all those storage parameters, which are already divided by type: per-table and per-index. A new section called "Storage Parameters" in the chapter "Server Configuration", just after "Query Planning" for example would make sense. Then we could have a section for indexes parameters, one for tables, and one for parameters shared between both, like fillfactor. Then we would need to add to link to this new section in the pages of CREATE/ALTER TABLE/INDEX. Does that make sense? The fact that we have per-index and per-table parameters is perhaps an argument sufficient to keep things the way they are now, though we had better add an indexterm for example for fillfactor. -- Michael -- Sent via pgsql-hackers mailing list (email@example.com) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers