Bloat doesn't depend on your update/delete rate; it depends on how many
update/deletes occur between vacuums. Long running transactions also
come into play.
As for performance, a P4 with 512M of ram is pretty much a toy in the
database world; it wouldn't be very hard to swamp it.
But without actu
Hi all and thanks for your responses. I haven't yet had a chance to
tweak the autovac settings but I really don't think that things can be
maxing out even the default settings.
We have about 4 machines that are connected 24/7 - they were doing
constant read/inserts (24/7) but that was because the
Joshua D. Drake wrote:
- in our env, clients occasionally hit max_connections. This is a
known and (sort of) desired pushback on load. However, that sometimes
knocks pg_autovacuum out.
That is when you use:
superuser_reserved_connections
Blush. Good point. Though, when we hit max_connection
Mischa Sandberg wrote:
Andrew Sullivan wrote:
On Thu, Jun 01, 2006 at 01:54:08PM +0200, Antoine wrote:
Hi,
We just don't seem to be getting much benefit from autovacuum. Running
a manual vacuum seems to still be doing a LOT, which suggests to me
that I should either run a cron job and disable a
Andrew Sullivan wrote:
On Thu, Jun 01, 2006 at 01:54:08PM +0200, Antoine wrote:
Hi,
We just don't seem to be getting much benefit from autovacuum. Running
a manual vacuum seems to still be doing a LOT, which suggests to me
that I should either run a cron job and disable autovacuum, or just
run a
On Thu, Jun 01, 2006 at 01:54:08PM +0200, Antoine wrote:
> Hi,
> We just don't seem to be getting much benefit from autovacuum. Running
> a manual vacuum seems to still be doing a LOT, which suggests to me
> that I should either run a cron job and disable autovacuum, or just
> run a cron job on top
On Thu, Jun 01, 2006 at 11:05:55AM -0400, Tom Lane wrote:
> Antoine <[EMAIL PROTECTED]> writes:
> > We just don't seem to be getting much benefit from autovacuum. Running
> > a manual vacuum seems to still be doing a LOT, which suggests to me
> > that I should either run a cron job and disable auto
Antoine <[EMAIL PROTECTED]> writes:
> We just don't seem to be getting much benefit from autovacuum. Running
> a manual vacuum seems to still be doing a LOT, which suggests to me
> that I should either run a cron job and disable autovacuum, or just
> run a cron job on top of autovacuum.
The defaul
Hi,
We just don't seem to be getting much benefit from autovacuum. Running
a manual vacuum seems to still be doing a LOT, which suggests to me
that I should either run a cron job and disable autovacuum, or just
run a cron job on top of autovacuum.
The problem is that if I run the same query (an up
