From: Dave Cramer <pg@fastcrypt.com>
To: Matteo Sgalaberni <sgala@sgala.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: database bloat, non removovable rows, slow query etc... [RESOLVED]
Date: Sat, 2 Sep 2006 10:16:36 -0400
Message-ID: <F4EC74C4-45F9-44D3-8912-8A0729C9D3F3@fastcrypt.com> (raw)
In-Reply-To: <20060902083725.GB2266@sgala.com>
References: <20060901123915.GT2266@sgala.com>
<4027.1157121810@sss.pgh.pa.us>
<20060901172829.GX2266@sgala.com>
<12756.1157132120@sss.pgh.pa.us>
<20060902083725.GB2266@sgala.com>
Matteo,
On 2-Sep-06, at 4:37 AM, Matteo Sgalaberni wrote:
> On Fri, Sep 01, 2006 at 01:35:20PM -0400, Tom Lane wrote:
>> Matteo Sgalaberni <sgala@sgala.com> writes:
>>> Ok. I stopped all clients. No connections to this database.
>>
>> When you say "this database", do you mean the whole postmaster
>> cluster,
>> or just the one database? Open transactions in other databases of
>> the
>> same cluster can be a problem.
>>
> AGH!!!! AGHR!!!
>
> A my collegue JDBC application that stay in "idle intransaction"
> 24h/24h
> (but in another database, non in the bloated-reported db...)!
>
> I killed it now(jdbc app).
this behaviour has been fixed in later versions of the jdbc driver
>
> vacuumed full and PG have cleaned all!! So if I have a idle
> transaction in
> one database of the cluster it "lock" vacuums of all databases of
> the cluster.
>
> Good to know this...but why this behaviour? it'is lovely...:)
>
> Tom , can you explain why?...
>
> Thanks a lot!!
>
> Matteo
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>
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-performance@postgresql.org
Cc: pg@fastcrypt.com, sgala@sgala.com, tgl@sss.pgh.pa.us
Subject: Re: database bloat, non removovable rows, slow query etc... [RESOLVED]
In-Reply-To: <F4EC74C4-45F9-44D3-8912-8A0729C9D3F3@fastcrypt.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