From: | Matteo Sgalaberni <sgala(at)sgala(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: database bloat, non removovable rows, slow query etc... [RESOLVED] |
Date: | 2006-09-02 08:37:25 |
Message-ID: | 20060902083725.GB2266@sgala.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
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).
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
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Cramer | 2006-09-02 14:16:36 | Re: database bloat, non removovable rows, slow query etc... [RESOLVED] |
Previous Message | Joshua D. Drake | 2006-09-02 00:24:18 | Re: increasing shared buffers: how much should be removed |