On Sat, 2003-08-09 at 21:25, Christopher Browne wrote:
> In 7.3 and 7.4, the "contrib" application, pg_autovacuum can do the
> trick, vacuuming anything that reaches thresholds of
> inserts/deletes/updates, and do so more or less as often as necessary.
Actually pg_autovacuum is not included with
Martijn van Oosterhout wrote:
Have you run VACUUM and/or VACUUM FULL and/or ANALYZE recently?
a) yes. I have it run analyze every 30 minutes or 1600 record
additions. Records are never updated or deleted so I assume I don't
need vacuum.
b) It does it even at start up when there are fewer t
I have one process which writes a single float into 300 columns once per
second. I then run 4 process, from remote computers, to query a small
subset of the latest row.
I have even commented out everything in the query programs, all they do
is sleep, and the associated postmaster still sucks u
On Sat, Aug 09, 2003 at 05:45:59PM -0300, Claudio Lapidus wrote:
> > Run VACUUM VERBOSE on it; you'll no doubt see that some internal
> > tables such as pg_activity, pg_statistic, and such have a lot of dead
> > tuples. Establishing a connection leads to _some_ DB activity, and
> > probably a dead
Oops! [EMAIL PROTECTED] (Chris Webster) was seen spray-painting on a wall:
> Martijn van Oosterhout wrote:
>
>>Have you run VACUUM and/or VACUUM FULL and/or ANALYZE recently?
>>
> a) yes. I have it run analyze every 30 minutes or 1600 record
> additions. Records are never updated or deleted so I
Have you run VACUUM and/or VACUUM FULL and/or ANALYZE recently?
On Thu, Aug 07, 2003 at 05:44:05PM -0600, Chris Webster wrote:
> I have one process which writes a single float into 300 columns once per
> second. I then run 4 process, from remote computers, to query a small
> subset of the lates
