| From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
|---|---|
| To: | Csaba Nagy <nagy(at)ecircle-ag(dot)com> |
| Cc: | Shelby Cain <alyandon(at)yahoo(dot)com>, Postgres general mailing list <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: allow LIMIT in UPDATE and DELETE |
| Date: | 2006-05-23 22:12:00 |
| Message-ID: | 20060523221159.GF64371@pervasive.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, May 23, 2006 at 10:19:25AM +0200, Csaba Nagy wrote:
> On Mon, 2006-05-22 at 23:55, Jim C. Nasby wrote:
> > BTW, there's a bug/issue with CLUSTER that makes it not entirely
> > transaction safe.
>
> For God's sake, don't fix that one ! I rely on it... now seriously,
> until there's a way to tell the DB that an exclusive lock is enough to
> vacuum all dead rows, even if they would be visible by other
> transactions, CLUSTER is the only thing I can use to circumvent the long
> running transaction syndrome.
I believe it's already fixed in HEAD/8.2.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2006-05-23 22:13:06 | Re: [GENERAL] Querying libpq compile time options |
| Previous Message | Jim C. Nasby | 2006-05-23 22:11:10 | Re: allow LIMIT in UPDATE and DELETE |