Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125])
	by mail.postgresql.org (Postfix) with ESMTP id 6555D14C2166
	for <pgsql-admin@postgresql.org>; Mon, 23 Jul 2012 21:35:47 -0300 (ADT)
Received: from mail-pb0-f46.google.com ([209.85.160.46])
	by makus.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <ringerc@ringerc.id.au>) id 1StT6E-0004fZ-LK
	for pgsql-admin@postgresql.org; Tue, 24 Jul 2012 00:35:47 +0000
Received: by pbbrp8 with SMTP id rp8so11717446pbb.19
	for <pgsql-admin@postgresql.org>; Mon, 23 Jul 2012 17:35:28 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=message-id:date:from:user-agent:mime-version:to:cc:subject
	:references:in-reply-to:content-type:x-gm-message-state;
	bh=RJo0fUpqmSa6FjrrVx3985dwQtkZI8B147jbhA1h6y4=;
	b=QyqmSi4n9abV4C6o/oPya0h/t7Q60aqCdrF/jr3w1wIZCJUA2LC9Y+o+VT3CZ8Hqsy
	xIv1Ulh3wwRDbyglZHsCv7P4Y301Qx++W5eEmetbQMbZoNHoIrEz+WY/bmRTBf8X7Pss
	e4KlKwK/JxUHwVjbj/RW6qnMa9vlitvVtY3Jzx6JnzJidTpiRXHPxDG7jsFS2d5GWs3q
	mb7YBfm5uCKTh2q3NQlk0pEpzdr2+IfLEjIvRHv/NC6dJHc480BKMzEIxi4uzllr5iCQ
	56nEm2hRR+joq1dCEH4CdkSG01AcpVYcNhb4pRTLujscDuCZB2WKgvFxohRPg/PpFUE3
	arCw==
Received: by 10.68.238.232 with SMTP id vn8mr39857340pbc.78.1343090128315;
	Mon, 23 Jul 2012 17:35:28 -0700 (PDT)
Received: from ayaki.localdomain ([114.75.214.115])
	by mx.google.com with ESMTPS id tq4sm10956543pbc.11.2012.07.23.17.35.25
	(version=SSLv3 cipher=OTHER); Mon, 23 Jul 2012 17:35:27 -0700 (PDT)
Message-ID: <500DEDC7.3000402@ringerc.id.au>
Date: Tue, 24 Jul 2012 08:35:19 +0800
From: Craig Ringer <ringerc@ringerc.id.au>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:14.0) Gecko/20120717 Thunderbird/14.0
MIME-Version: 1.0
To: Gary Webster <webster@lexmark.com>
CC: pgsql-admin@postgresql.org
Subject: Re: db size growing out of control when using clustered Jackrabbit
References: 
 <CAEHjwJ6pu1D+nQEbdg=bimY0gKVFvBTVq6JoMQjt3v3_ChMncA@mail.gmail.com>
In-Reply-To: 
 <CAEHjwJ6pu1D+nQEbdg=bimY0gKVFvBTVq6JoMQjt3v3_ChMncA@mail.gmail.com>
Content-Type: multipart/alternative;
	boundary="------------040904010003090204010206"
X-Gm-Message-State: 
 ALoCoQluF6P+kj95cmkfDntXXVUFDfsxGe3VPO6hbRzvvK/YRmMdA+qNTcQnSucCp4lrr6cG9eSE
X-Pg-Spam-Score: -1.9 (-)
X-Archive-Number: 201207/64
X-Sequence-Number: 39781

This is a multi-part message in MIME format.
--------------040904010003090204010206
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

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

--------------040904010003090204010206
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 07/24/2012 05:13 AM, Gary Webster
      wrote:<br>
    </div>
    <blockquote
cite="mid:CAEHjwJ6pu1D+nQEbdg=bimY0gKVFvBTVq6JoMQjt3v3_ChMncA@mail.gmail.com"
      type="cite">
      <meta http-equiv="Context-Type" content="text/html;
        charset=ISO-8859-1">
      Hello. I'm hoping someone has seen this before.<br>
      <br>
      We are trying to use Postgres Plus v9.1.3 as the Persistence
      Manager in Jackrabbit (Apache JCR) clustering (<a
        moz-do-not-send="true"
        href="http://wiki.apache.org/jackrabbit/Clustering"
        target="_blank">http://wiki.apache.org/jackrabbit/Clustering</a>).<br>
      Whenever the JCR is under load, the ws_bundle TOAST table in the&nbsp;
      repository&nbsp; schema, grows out of control !<br>
    </blockquote>
    <br>
    Has somebody disabled autovacuum or set it to barely run at all?<br>
    <br>
    Try setting autovacuum to very aggressively vacuum the problem
    table(s).<br>
    <br>
    --<br>
    Craig Ringer<br>
  </body>
</html>

--------------040904010003090204010206--