Eric Brown <[EMAIL PROTECTED]> writes:
> My application is multi-threaded and I could care less about the concurrency
> afforded by MVCC. I'd rather just update the things in place and get less
> postgresql concurrency but more consistent long-running performance and disk
> space utilization.
Po
> "MvO" == Martijn van Oosterhout writes:
MvO> I'd suggest, use the autovacuum daemon, tune your FSM settings to what
MvO> you expect the load to be and maybe schedule a database-wide
MvO> REINDEX/VACUUM FULL regularly. We found doing it once a month was
MvO> enough to keep it tip-top over th
On Tue, Dec 28, 2004 at 02:40:52AM -0800, Eric Brown wrote:
> I'm building an appliance where I don't want my customers having to
> tune postgresql in any way from the configuration when I install it. I
> don't even want them to know it is there. Yet in my study of posgresql,
> it seems that eve
I'm building an appliance where I don't want my customers having to
tune postgresql in any way from the configuration when I install it. I
don't even want them to know it is there. Yet in my study of posgresql,
it seems that even conscientious use of a vacuum daemon or cron job in
vacuum's vari
