Title: Message
You
are pulling a fair amount of data from the database and doing a lot of
computation in the SQL. I'm not sure how fast this query could be expected
to run, but I had one idea. If you've
inserted and deleted a lot into this table, you will need to run vacuum
ocasionally.
"Bealach-na Bo" <[EMAIL PROTECTED]> wrote:
> >If you don't need access to the old data constantly:
> >
> > - copy the live data to a new table
> > - TRUNCATE the old table (which needs an exclusive lock but is very fast)
> > - insert the data back in
> > - for an event log I would imagine this
Gregory Stewart wrote:
Hello,
We are currently developing a web application and have the webserver and
PostgreSQL with our dev db running on a machine with these specs:
Win 2003 standard
AMD Athlon XP 3000 / 2.1 GHZ
2 Gig ram
120 gig SATA HD
PostgreSQL 8.1.0
Default pgsql configuration + shar
If you don't need access to the old data constantly:
- copy the live data to a new table
- TRUNCATE the old table (which needs an exclusive lock but is very fast)
- insert the data back in
- for an event log I would imagine this could work
Obtaining exclusive locks on this table is very dif
