From: Tom Lane <tgl@sss.pgh.pa.us>
To: Gary Webster <webster@lexmark.com>
Cc: pgsql-admin@postgresql.org, "Joshua D. Drake" <jd@commandprompt.com>
Subject: Re: db size growing out of control when using clustered Jackrabbit
Date: Tue, 24 Jul 2012 13:08:35 -0400
Message-ID: <24028.1343149715@sss.pgh.pa.us> (raw)
In-Reply-To: <CAEHjwJ75MB1jm0W516w1YJt7NJ35a=pHaPPtMf1z+SX=G+9qLA@mail.gmail.com>
References: <CAEHjwJ6pu1D+nQEbdg=bimY0gKVFvBTVq6JoMQjt3v3_ChMncA@mail.gmail.com>
<500DC4BB.2090102@commandprompt.com>
<CAEHjwJ75MB1jm0W516w1YJt7NJ35a=pHaPPtMf1z+SX=G+9qLA@mail.gmail.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, webster@lexmark.com, jd@commandprompt.com
Subject: Re: db size growing out of control when using clustered Jackrabbit
In-Reply-To: <24028.1343149715@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox