Re: temporary statistics option at initdb time - Mailing list pgsql-hackers

From Tom Lane
Subject Re: temporary statistics option at initdb time
Date
Msg-id 8763.1218600873@sss.pgh.pa.us
Whole thread Raw
In response to Re: temporary statistics option at initdb time  (Decibel! <decibel@decibel.org>)
Responses Re: temporary statistics option at initdb time  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
Decibel! <decibel@decibel.org> writes:
> I disagree. While we don't guarantee stats are absolutely up-to-date,  
> or atomic I don't think that gives license for them to just magically  
> not exist sometimes.

> Would it really be that hard to have the system copy the file out  
> before telling all the other backends of the change?

Well, there is no (zero, zilch, nada) use-case for changing this setting
on the fly.  Why not make it a "frozen at postmaster start" GUC?  Seems
like that gets all the functionality needed and most of the ease of use.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Transaction-controlled robustness for replication
Next
From: Simon Riggs
Date:
Subject: Re: SeqScan costs