"Jeremy M. Guthrie" <[EMAIL PROTECTED]> writes:
> I looked back at my code and I also need to reclarify something. The delete
> at the end is multiple delete statements within a transaction.
I think you are going to have to show us all the details of what you're
doing in between these queries.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I looked back at my code and I also need to reclarify something. The delete
at the end is multiple delete statements within a transaction.
After full vacuum with 160,000 records in Table: (takes a bit the first time
through)
Tlog=# explain analyze
On Sat, 19 Jul 2003, Jeremy M. Guthrie wrote:
> 100megs of new data each day. However, the instant the system finishes only
> a 'vacuum analyze', the whole thing slows WAY down to where each run can take
> 10-15 minutes.
Have you run EXPLAIN ANALYZE on the delete query before and after the
va
"Jeremy M. Guthrie" <[EMAIL PROTECTED]> writes:
> My system will run great after a full vacuum(as I would expect). It will run
> all day long taking only 3-5 seconds to run and deal with approximately
> 100megs of new data each day. However, the instant the system finishes only
> a 'vacu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I have an application I wrote that uses two tables heavily. The first table
is a queue table, the second table is an archive table. The queue table is
constantly taking on new records at the rate of 10/second. My software pulls
th
