| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Florian Eberle <florian(dot)eberle(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Force removing Locks |
| Date: | 2008-07-10 15:06:01 |
| Message-ID: | 1999.1215702361@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Florian Eberle <florian(dot)eberle(at)gmail(dot)com> writes:
> I've got a Problem... An Application that uses my Postgres Server always
> keeps some locks open... Is there a Possibility to forcing remove the
> Locks after a certain Interval or to remove them by hand?
Fix your application to close its transaction occasionally. Leaving
a transaction open forever prevents vacuum from cleaning dead rows,
quite independently of any locking issues.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | A. Kretschmer | 2008-07-10 15:08:03 | Re: SPACE FOR POSTGRESQL DATABASE |
| Previous Message | Ivan Sergio Borgonovo | 2008-07-10 14:56:33 | Re: expected O^2 looks line K^O, index problem not involved: [was] looping simpler query just faster |