Log In - Home Page

Patch: Optimization for updating foreign tables in Postgres FDW

Edit Patch - Move To Another CommitFest - Delete Patch

CommitFest 2014-08
Topic Performance
Patch Status Returned with Feedback
Author Etsuro Fujita
Reviewers Shigeru Hanada, Laurenz Albe
Committer Tom Lane
Close Date 2014-09-23
Comments
Patch by efujita on 2014-07-08 09:45:59 AM: Initial version.
Patch by efujita on 2014-08-04 11:57:48 AM: v2 addressing the comments from Eitoku-san, adding regression tests, fixing a bug
Review by laurenz on 2014-08-25 01:59:37 PM: Review by Shigeru Hanada:
- Problem with DELETE triggers
- DELETE triggers need not prohibit UPDATE optimization and vice versa
- Documentation nees more love
Review by laurenz on 2014-08-25 02:00:50 PM: Surprising "actual time" values with EXPLAIN ANALYZE
Patch by efujita on 2014-09-01 03:26:36 AM: v3 addressing the above review comments
Review by laurenz on 2014-09-02 01:48:15 PM: Review by Etsuro Fujita shows clear performance gain.
Review by laurenz on 2014-09-02 01:50:41 PM: Behaviour is ok.
Are SelectFdwScanPrivateLength and UpdateFdwScanPrivateLength the best way to differentiate between normal and pushed down updates?
Patch by efujita on 2014-09-08 11:20:39 AM: v4 addressing the comments from Laurenz
Comment by sfrost on 2014-09-23 02:40:21 AM: Comments that this is most likely not the right approach.
Comment by sfrost on 2014-09-23 02:40:40 AM: Furhter comments on approach.
Comment by sfrost on 2014-09-23 02:41:27 AM: Comments from author and indication that it'll be worked on in the next CF, marking 'returned with feedback'

Add Comment

Please log in to comment on this patch.