From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Daniel Loureiro <daniel(at)termasa(dot)com(dot)br>, Jaime Casanova <jaime(at)2ndquadrant(dot)com>, Csaba Nagy <ncslists(at)googlemail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: DELETE with LIMIT (or my first hack) |
Date: | 2010-12-03 00:26:35 |
Message-ID: | 201012030026.oB30QZ927456@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert Haas wrote:
> On Thu, Dec 2, 2010 at 7:12 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> > Peter Eisentraut wrote:
> >> On tis, 2010-11-30 at 14:20 -0500, Andrew Dunstan wrote:
> >> > I agree, that argument is completely misconceived. If the DBA is
> >> > paying enough attention to use LIMIT, s/he should be paying enough
> >> > attention not to do damage in the first place. If that were the only
> >> > argument in its favor I'd be completely against the feature.
> >>
> >> I don't have any use for DELETE with LIMIT, but UPDATE with LIMIT could
> >> be very useful if you are doing full-table updates and you don't have
> >> enough space so you do it in chunks.
> >
> > So should this now be a TODO item? ?Text?
>
> Allow DELETE and UPDATE to be used with LIMIT and ORDER BY.
Done:
Allow DELETE and UPDATE to be used with LIMIT and ORDER BY
* http://archives.postgresql.org/pgsql-hackers/2010-11/msg01997.php
* http://archives.postgresql.org/pgsql-hackers/2010-12/msg00021.php
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2010-12-03 00:32:44 | Re: should we set hint bits without dirtying the page? |
Previous Message | Andrew Dunstan | 2010-12-03 00:21:28 | Re: WIP patch for parallel pg_dump |