Hi,
Every time i explain what is the fsync parameter for, the next thing i always say is: "never turn it off", and now that we have synchronous_commit there is no good reason for turn fsync off... so why are we still let it be in the postgresql.conf where it's so vulnerable to a misguided dba? even just not show it should be great. another parameter that is interesting is seq_page_cost, AFAIUI all the other cost parameters (in the planner section of course) are relative to this one. so what is the logic in allow changing it? going a little further, when we have this per tablespace what will mean to change a tablespace seq_page_cost? it will be relative to the general one? -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL AsesorÃa y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
