Re: LIMIT for UPDATE and DELETE - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: LIMIT for UPDATE and DELETE
Date
Msg-id CAA4eK1KaZ2kzuDRzVWOeRzhfTkD261uLG7sFw_ceWmTkZZYbNQ@mail.gmail.com
Whole thread Raw
In response to Re: LIMIT for UPDATE and DELETE  (Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp>)
List pgsql-hackers
On Mon, Aug 25, 2014 at 12:18 PM, Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp> wrote:
> (2014/08/15 6:18), Rukh Meski wrote:
>>
>> Based on the feedback on my previous patch, I've separated only the
>> LIMIT part into its own feature.  This version plays nicely with
>> inheritance.  The intended use is splitting up big UPDATEs and DELETEs
>> into batches more easily and efficiently.
>
>
> Before looking into the patch, I'd like to know the use cases in more details.

You can once check the previous commit fest thread [1] for
this feature, in that you can find some use cases and what are
the difficulties to implement this feature, it might aid you in
review of this feature.

pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Escaping from blocked send() reprised.
Next
From: Albe Laurenz
Date:
Subject: Re: Optimization for updating foreign tables in Postgres FDW