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

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

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Gary Webster <webster(at)lexmark(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: db size growing out of control when using clustered Jackrabbit
Date: 2012-07-27 18:11:34
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
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.



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

In response to

pgsql-admin by date

Next:From: Majid AzimiDate: 2012-07-30 05:42:17
Subject: VACUUM ANALYZE block the whole database
Previous:From: Tom LaneDate: 2012-07-27 16:12:38
Subject: Re: pg_dump on Postgres 9.1

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