Re: temporary statistics option at initdb time

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Decibel! <decibel(at)decibel(dot)org>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, pgsql-hackers(at)postgresql(dot)org, Euler Taveira de Oliveira <euler(at)timbira(dot)com>
Subject: Re: temporary statistics option at initdb time
Date: 2008-08-13 04:14:33
Message-ID: 8763.1218600873@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Decibel! <decibel(at)decibel(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-08-13 04:20:55 Re: Replay attack of query cancel
Previous Message Bruce Momjian 2008-08-13 04:04:23 Re: Plugin system like Firefox