Re: db size growing out of control when using clustered Jackrabbit

On 07/24/2012 08:58 AM, Gary Webster wrote:
> Hello.
> Thanks for the response.
>
> There are several 'idle in transaction' on this server/app, but to a
> different db/schema.

This is a cluster issue, not a database issue. So if you have an idnle
in transaction, then it is affecting your JCR schema as well.

> The "repository" (JCR) schema has only a few 'idle', none 'in transaction' .

>
> By "routine maintenance", do you mean autovacuum, or something else?

I mean autovacuum.

> Autovacuum does appear to usually get 'auto-canceled' by a lock.

That is a problem too.

> However, even when it runs successfully, it doesn't seem to help with
> this ws_bundle Toast table size.

It won't if you have the above idle in transactions, regardless of database.

Sincerely,

jD

--
Command Prompt, Inc. - http://www.commandprompt.com/
PostgreSQL Support, Training, Professional Services and Development
High Availability, Oracle Conversion, Postgres-XC
@cmdpromptinc - 509-416-6579