| From: | Matthew Wakeling <matthew(at)flymine(dot)org> |
|---|---|
| To: | Lorenzo Allegrucci <lorenzo(dot)allegrucci(at)forinicom(dot)it> |
| Cc: | pgsql-performance(at)postgresql(dot)org, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: [PERFORM] Strange performance degradation |
| Date: | 2009-11-24 11:14:12 |
| Message-ID: | alpine.DEB.2.00.0911241108530.684@aragorn.flymine.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-performance |
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 thoroughly confuse the client
application, you can send a TERM signal to a backend, but the consequences
to your data are on your own head.
Fix the application, don't tell Postgres to stop being a decent database.
Matthew
--
I would like to think that in this day and age people would know better than
to open executables in an e-mail. I'd also like to be able to flap my arms
and fly to the moon. -- Tim Mullen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alban Hertroys | 2009-11-24 11:28:43 | Re: Multicolumn index including tsvector. |
| Previous Message | Allan Morris Caras | 2009-11-24 11:12:51 | Re: [COMMITTERS] recover deleted records |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | ramasubramanian | 2009-11-24 11:25:56 | Dynamic sql example |
| Previous Message | Sam Jas | 2009-11-24 09:50:35 | Re: Strange performance degradation |