Re: [PERFORM] Very long deletion time on a 200 GB database

2012-02-25 Thread Reuven M. Lerner
Hi, everyone. Jeff wrote: Is this 9 hours run time for deleting one day worth of data, or for deleting the entire accumulation of cruft that filled up the hard drive in the first place (which would be 170 days, if you have 200GB that accumulated at 1GB per day and you only need 30 days) ? Unf

Re: [PERFORM] PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory?

2012-02-25 Thread Jeff Janes
On Sat, Feb 25, 2012 at 4:16 PM, Stefan Keller wrote: > > I'd like to come back on the issue of aka of in-memory key-value database. > > To remember, it contains table definition and queries as indicated in > the appendix [0]. There exist 4 other tables of similar structure. > There are indexes on

[PERFORM] PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory?

2012-02-25 Thread Stefan Keller
Hi, 2011/10/24 Stephen Frost wrote > Now, we've also been discussing ways to have PG automatically > re-populate shared buffers and possibly OS cache based on what was in > memory at the time of the last shut-down, but I'm not sure that would > help your case either since you're rebuilding everyt

Re: [PERFORM] Very long deletion time on a 200 GB database

2012-02-25 Thread Jeff Janes
On Thu, Feb 23, 2012 at 12:39 AM, Reuven M. Lerner wrote: > Hi, everyone.  I'm maintaining an application that exists as a "black box" > in manufacturing plants.  The system is based on Windows, .NET, and > PostgreSQL 8.3.  I'm a Unix kind of guy myself, but the application layer > and system admi