Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125]) by mail.postgresql.org (Postfix) with ESMTP id 254F7F64990 for ; Tue, 24 Jul 2012 14:42:06 -0300 (ADT) Received: from 30.55.colo.spiretech.net ([69.168.55.30] helo=lists.commandprompt.com) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Stj7V-0004f4-Un for pgsql-admin@postgresql.org; Tue, 24 Jul 2012 17:42:06 +0000 Received: from [192.168.1.5] (spinlock.commandprompt.com [69.168.55.30]) by lists.commandprompt.com (Postfix) with ESMTPA id ECA1E10; Tue, 24 Jul 2012 10:41:52 -0700 (PDT) Received: from [192.168.1.5] ([68.118.161.194] helo=[192.168.1.5]) by assp.commandprompt.com with ESMTPS(AES256-SHA) (2.1.1); 24 Jul 2012 10:41:52 -0700 Message-ID: <500EDE55.9060409@commandprompt.com> Date: Tue, 24 Jul 2012 10:41:41 -0700 From: "Joshua D. Drake" Organization: Command Prompt, Inc. User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0 MIME-Version: 1.0 To: Gary Webster CC: pgsql-admin@postgresql.org Subject: Re: db size growing out of control when using clustered Jackrabbit References: <500DC4BB.2090102@commandprompt.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Assp-Version: 2.1.1(11364) on assp.commandprompt.com X-Assp-Client-SSL: yes X-Assp-ID: assp.commandprompt.com m1-51712-02452 X-Assp-Envelope-From: jd@commandprompt.com X-Assp-Intended-For: webster@lexmark.com X-Assp-Original-Subject: Re: [ADMIN] db size growing out of control when using clustered Jackrabbit X-Pg-Spam-Score: -1.9 (-) X-Archive-Number: 201207/68 X-Sequence-Number: 39785 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