Skip site navigation (1) Skip section navigation (2)

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

From: Gary Webster <webster(at)lexmark(dot)com>
To: pgsql-admin(at)postgresql(dot)org
Subject: Re: db size growing out of control when using clustered Jackrabbit
Date: 2012-07-24 15:34:57
Message-ID: CAEHjwJ6tkup-=wgtNp=Z7-uciTDBbMO+XCvcVdT=+9R6Op9OdQ@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-admin
Hello.
Thanks for the response.

Autovacuum is set VERY aggressive.
However, it does not help with the ws_bundle Toast table.

A manual _full_ vacuum (not recommended?) does do the deed.
However, it often gives this error:
ERROR:  missing chunk number 0 for toast value 639113 in pg_toast_533386

BTW, how bad is that?  Corruption?


On Mon, Jul 23, 2012 at 8:35 PM, Craig Ringer <ringerc(at)ringerc(dot)id(dot)au> wrote:

>  On 07/24/2012 05:13 AM, Gary Webster wrote:
>
> Hello. I'm hoping someone has seen this before.
>
> We are trying to use Postgres Plus v9.1.3 as the Persistence Manager in
> Jackrabbit (Apache JCR) clustering (
> http://wiki.apache.org/jackrabbit/Clustering).
> Whenever the JCR is under load, the ws_bundle TOAST table in the
> repository  schema, grows out of control !
>
>
> Has somebody disabled autovacuum or set it to barely run at all?
>
> Try setting autovacuum to very aggressively vacuum the problem table(s).
>
> --
> Craig Ringer
>

In response to

pgsql-admin by date

Next:From: Gary WebsterDate: 2012-07-24 15:58:53
Subject: Re: db size growing out of control when using clustered Jackrabbit
Previous:From: Craig RingerDate: 2012-07-24 00:35:19
Subject: Re: db size growing out of control when using clustered Jackrabbit

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group