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

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

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: Gary Webster <webster(at)lexmark(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Subject: Re: db size growing out of control when using clustered Jackrabbit
Date: 2012-07-26 20:05:19
Message-ID: CAOR=d=3AJ4GXn8+_E_VrNxyNzqE8_8a4Nt6taexT2ZHuV6FZJQ@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-admin
On Thu, Jul 26, 2012 at 1:31 PM, Gary Webster <webster(at)lexmark(dot)com> 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.

That's crazy big.  Is that a normal payload size for this app?

In response to

pgsql-admin by date

Next:From: Alanoly AndrewsDate: 2012-07-27 15:49:44
Subject: pg_dump on Postgres 9.1
Previous:From: Gary WebsterDate: 2012-07-26 19:31:48
Subject: Re: db size growing out of control when using clustered Jackrabbit

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