| From: | Marko Tiikkaja <marko(at)joh(dot)to> |
|---|---|
| To: | Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>, 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-08-29 11:56:13 |
| Message-ID: | 54006A5D.4000500@joh.to |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 8/29/14 1:53 PM, I wrote:
> This is just my personal opinion, but what I think should happen is:
>
> 1) We put the LIMIT inside ModifyTable like this patch does. This
> doesn't prevent us from doing ORDER BY in the future, but helps numerous
> people who today have to
Oops, looks like I didn't finish my thought here.
.. but helps numerous people who today have to achieve the same thing
via tedious, slow and problematic subqueries (or a choose-any-two
combination of these).
.marko
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2014-08-29 12:14:12 | Re: Question about coding of free space map |
| Previous Message | Marko Tiikkaja | 2014-08-29 11:53:16 | Re: LIMIT for UPDATE and DELETE |