| From: | Rukh Meski <rukh(dot)meski(at)yahoo(dot)ca> |
|---|---|
| To: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: 9.5: UPDATE/DELETE .. ORDER BY .. LIMIT .. |
| Date: | 2014-03-12 21:12:26 |
| Message-ID: | 1394658746.44147.YahooMailNeo@web163006.mail.bf1.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
Here's an updated patch. I had to push the LIMIT processing into ModifyTable to make the behaviour sane in parallel scenarios. As usual, please ignore if you're busy with 9.4. I will work on better docs and more tests from now on and am preparing to make a solid case for adding this.
♜
| Attachment | Content-Type | Size |
|---|---|---|
| update_delete_order_by_limit_v1.diff | application/octet-stream | 25.2 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2014-03-12 21:30:27 | Re: Performance Improvement by reducing WAL for Update Operation |
| Previous Message | Andrew Dunstan | 2014-03-12 21:09:26 | Re: jsonb and nested hstore |