| From: | Marko Tiikkaja <marko(at)joh(dot)to> |
|---|---|
| To: | Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Rukh Meski <rukh(dot)meski(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: LIMIT for UPDATE and DELETE |
| Date: | 2014-09-10 10:18:41 |
| Message-ID: | 54102581.2020207@joh.to |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 9/10/14 12:05 PM, Etsuro Fujita wrote:
> (2014/09/10 18:33), Marko Tiikkaja wrote:
>> You can already change *this patch* to do ModifyTable <- Limit <-
>> LockRows. If we think that's what we want, we should rewrite this patch
>> right now.
>
> I think it might be relatively easy to do that for single-table cases,
> but for inheritance cases, inheritance_planner needs work and I'm not
> sure how much work it would take ...
Uh. Yeah, I think I'm an idiot and you're right.
I'll try and get some benchmarking done and see what comes out.
.marko
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2014-09-10 10:39:23 | Re: replication commands and log_statements |
| Previous Message | Etsuro Fujita | 2014-09-10 10:05:25 | Re: LIMIT for UPDATE and DELETE |