On Fri, Jan 1, 2010 at 12:21 PM, Tom Lane wrote:
>
>> 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?
>
> Please read the discussions that went
Tom Lane wrote:
> Jaime Casanova writes:
>> 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
Jaime Casanova writes:
> 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
> vulne
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?
ev
