From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
---|---|
To: | Matteo Sgalaberni <sgala(at)sgala(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: database bloat, non removovable rows, slow query etc... [RESOLVED] |
Date: | 2006-09-02 14:16:36 |
Message-ID: | F4EC74C4-45F9-44D3-8912-8A0729C9D3F3@fastcrypt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
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(at)sgala(dot)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
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-09-02 14:21:23 | Re: database bloat, non removovable rows, slow query etc... [RESOLVED] |
Previous Message | Matteo Sgalaberni | 2006-09-02 08:37:25 | Re: database bloat, non removovable rows, slow query etc... [RESOLVED] |