Re: Feedback on auto-pruning approach - Mailing list pgsql-admin

From Mark Liberman
Subject Re: Feedback on auto-pruning approach
Date
Msg-id 9D938282F8C6EE43B748B910386DE93E0138B418@srvgpimail1.GPI.local
Whole thread Raw
In response to Feedback on auto-pruning approach  ("Mark Liberman" <mliberman@goldpocket.com>)
Responses Re: Feedback on auto-pruning approach  ("Jim C. Nasby" <jnasby@pervasive.com>)
List pgsql-admin

So, I have finally complete this auto-pruning solution.  It has proven effective in keeping the size of the db under whichever threshold I set in an unattended fashion.

I have one final question.  If my goal is to maximize the amount of historical data that we can keep - e.g. set the db size limit to be as large as possible - how much disk space should I reserve for standard Postgres operations - e.g. sort space, WAL, etc..  I'm sure this depends a bit on our configuration, etc.. but if someone can point me in the direction as to what factors I should consider, I'd greatly appreciate it.

Thanks,

Mark

pgsql-admin by date:

Previous
From: Amadeus Zilfinski
Date:
Subject: Re: Core 5 Upgrade
Next
From: lmyho
Date:
Subject: PostgreSQl newbie! -PLease help, pgAdmin3 on Debian!