From: Joshua D. Drake <jd@commandprompt.com>
To: Gary Webster <webster@lexmark.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: db size growing out of control when using clustered Jackrabbit
Date: Wed, 25 Jul 2012 11:44:44 -0700
Message-ID: <50103E9C.2050301@commandprompt.com> (raw)
In-Reply-To: <CAEHjwJ4qf2emMPKadyEkXyFVBbeMBNKjNo0ssTPfVGbxXfRazw@mail.gmail.com>
References: <CAEHjwJ6pu1D+nQEbdg=bimY0gKVFvBTVq6JoMQjt3v3_ChMncA@mail.gmail.com>
<500DC4BB.2090102@commandprompt.com>
<CAEHjwJ75MB1jm0W516w1YJt7NJ35a=pHaPPtMf1z+SX=G+9qLA@mail.gmail.com>
<500EDE55.9060409@commandprompt.com>
<CAEHjwJ4qf2emMPKadyEkXyFVBbeMBNKjNo0ssTPfVGbxXfRazw@mail.gmail.com>
On 07/25/2012 11:37 AM, Gary Webster wrote:
> 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.
>
> OK, how do I track/debug/stop the "idle in transaction"s ?
Well idle in transaction is ALWAYS a code issue. You have code that is
executing that is starting a transaction, leaving the connection open
while not closing (committing/rollingback) the transaction.
You could turn on query logging and make sure pid and timestamp is in
the log_line_prefix. They you can see what pids are idle in transaction
and trace to what the last query was.
o you mean autovacuum, or something else?
>
>
> I mean autovacuum.
>
> I was hoping to find more of a 'root cause' (eg. jackrabbit config) for
> this issue.
> I can't believe that this table is supposed to be getting so big, to
> even require much vacuuming.
Any update/delete to that table is going to cause bloat, autovacuum
cleans that up. If it can. If it can't, it will just continously grow.
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: jd@commandprompt.com, webster@lexmark.com
Subject: Re: db size growing out of control when using clustered Jackrabbit
In-Reply-To: <50103E9C.2050301@commandprompt.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox