Re: temporary statistics option at initdb time

On Aug 12, 2008, at 12:27 PM, Magnus Hagander wrote:
> I don't think it'd be that hard to handle the SIGHUP case - just have
> the stats collector start writing it in the new location the next time
> it writes it out, and backends will start reading from there.  
> There's a
> short window where the backends would get no data, but I think that's
> quite acceptable..


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?

BTW, it would be nice if it would actually remove the old file, but  
that sounds like a lot more work...
-- 
Decibel!, aka Jim C. Nasby, Database Architect  decibel@decibel.org
Give your computer some brain candy! www.distributed.net Team #1828