Re: db size growing out of control when using clustered Jackrabbit - Mailing list pgsql-admin

From Tom Lane
Subject Re: db size growing out of control when using clustered Jackrabbit
Date
Msg-id 24028.1343149715@sss.pgh.pa.us
Whole thread Raw
In response to Re: db size growing out of control when using clustered Jackrabbit  (Gary Webster <webster@lexmark.com>)
List pgsql-admin
Gary Webster <webster@lexmark.com> writes:
> By "routine maintenance", do you mean autovacuum, or something else?
> Autovacuum does appear to usually get 'auto-canceled' by a lock.

That's bad and you should look into the reason why it happens.  Ordinary
DML (CRUD) operations should not kick autovac off a table.  If it's
happening, it's probably because something is fooling with the table's
schema, which doesn't seem like something you want to have happening
during routine operations; especially not on tables that are large
enough for this to be an issue in the first place.  Or it might be
something doing a LOCK TABLE as a substitute for more fine-grained
locking; which again is bad for performance reasons that have nothing
to do with hobbling autovacuum.

            regards, tom lane

pgsql-admin by date:

Previous
From: Gary Webster
Date:
Subject: Re: db size growing out of control when using clustered Jackrabbit
Next
From: "Joshua D. Drake"
Date:
Subject: Re: db size growing out of control when using clustered Jackrabbit