Lorenzo Allegrucci escribió:
Matthew Wakeling wrote:
On Mon, 23 Nov 2009, Lorenzo Allegrucci wrote:
Anyway, how can I get rid those "idle in transaction" processes?
Can I just kill -15 them or is there a less drastic way to do it?
Are you crazy? Sure, if you want to destroy all of the changes
Matthew Wakeling wrote:
On Mon, 23 Nov 2009, Lorenzo Allegrucci wrote:
Anyway, how can I get rid those "idle in transaction" processes?
Can I just kill -15 them or is there a less drastic way to do it?
Are you crazy? Sure, if you want to destroy all of the changes made to
the database in that
On Mon, 23 Nov 2009, Lorenzo Allegrucci wrote:
Anyway, how can I get rid those "idle in transaction" processes?
Can I just kill -15 them or is there a less drastic way to do it?
Are you crazy? Sure, if you want to destroy all of the changes made to the
database in that transaction and thorough
t may help you!!!
--
Thanks
Sam Jas
--- On Mon, 23/11/09, Tom Lane wrote:
From: Tom Lane
Subject: Re: [GENERAL] Strange performance degradation
To: "Bill Moran"
Cc: "Lorenzo Allegrucci" ,
pgsql-performa...@postgresql.org, pgsql-general@postgresql.org
Date: Monday, 23 N
Bill Moran writes:
> In response to Lorenzo Allegrucci :
>> Tom Lane wrote:
>>> Are you killing off any long-running transactions when you restart?
>> Anyway, how can I get rid those "idle in transaction" processes?
>> Can I just kill -15 them or is there a less drastic way to do it?
> Connectio
In response to Lorenzo Allegrucci :
> Tom Lane wrote:
> > Lorenzo Allegrucci writes:
> >> So, my main question is.. how can just a plain simple restart of postgres
> >> restore the original performance (3% cpu time)?
> >
> > Are you killing off any long-running transactions when you restart?
>
Tom Lane wrote:
Lorenzo Allegrucci writes:
So, my main question is.. how can just a plain simple restart of postgres
restore the original performance (3% cpu time)?
Are you killing off any long-running transactions when you restart?
After three days of patient waiting it looks like the comm
Brian Modra wrote:
I had a similar problem: I did a large delete, and then a selct which
"covered" the previous rows.
It took ages, because the index still had those deleted rows.
Possibly the same happens with update.
Try this:
vacuum analyse
reindex database
(your database name instead of
Sam Jas wrote:
Is there any idle connections exists ?
I didn't see any, I'll look better next time.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Lorenzo Allegrucci writes:
> So, my main question is.. how can just a plain simple restart of postgres
> restore the original performance (3% cpu time)?
Are you killing off any long-running transactions when you restart?
regards, tom lane
--
Sent via pgsql-general maili
2009/11/20 Lorenzo Allegrucci :
>
> Hi all,
>
> I'm experiencing a strange behavior with my postgresql 8.3:
> performance is degrading after 3/4 days of running time but if I
> just restart it performance returns back to it's normal value..
> In normal conditions the postgres process uses about 3%
Is there any idle connections exists ?
--
Thanks
Sam Jas
--- On Fri, 20/11/09, Lorenzo Allegrucci
wrote:
From: Lorenzo Allegrucci
Subject: [GENERAL] Strange performance degradation
To: pgsql-performa...@postgresql.org
Cc: pgsql-general@postgresql.org
Date: Friday, 20 November, 2009, 9
Hi all,
I'm experiencing a strange behavior with my postgresql 8.3:
performance is degrading after 3/4 days of running time but if I
just restart it performance returns back to it's normal value..
In normal conditions the postgres process uses about 3% of cpu time
but when is in "degraded" condi
13 matches
Mail list logo
