Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id A1C69152A2F7 for ; Fri, 27 Jul 2012 15:12:10 -0300 (ADT) Received: from 30.55.colo.spiretech.net ([69.168.55.30] helo=lists.commandprompt.com) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Sup1C-0005Al-Sn for pgsql-admin@postgresql.org; Fri, 27 Jul 2012 18:12:09 +0000 Received: from [192.168.1.5] (spinlock.commandprompt.com [69.168.55.30]) by lists.commandprompt.com (Postfix) with ESMTPA id 300EAAC; Fri, 27 Jul 2012 11:11: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); 27 Jul 2012 11:11:51 -0700 Message-ID: <5012D9D6.8080002@commandprompt.com> Date: Fri, 27 Jul 2012 11:11:34 -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> <500EDE55.9060409@commandprompt.com> <50103E9C.2050301@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-12712-01759 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/99 X-Sequence-Number: 39816 On 07/26/2012 12:31 PM, Gary Webster wrote: > OK, I set "log_statement = "all"" > The log grew to 1GB in ~minute! It is dominated by this one statement, > which occurs every ~1.4 sec: > "update WS_BUNDLE set BUNDLE_DATA = $1 where NODE_ID_HI = $2 and > NODE_ID_LO = $3" > parameter $1 is hex, over 6million characters long !! Surely this is > the root of my problem. It definitely is. Every time you update, you are creating a dead tuple (unless it is HOT capable). If autovacuum can't come in behind and clean that up due to idle in transaction, you are going to have serious problems. 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