On Thu, 21 Feb 2019 at 10:32, Robert Haas <robertmh...@gmail.com> wrote: > I spent some time thinking about that exact issue this morning and > studying the code to try to figure that out. I wasn't able to find > any other places that seemed to need updating, but it could be that I > missed something that David also missed.
It looks like the comment that claimed the table was already locked crept back in during a (seemingly) sloppy rebase after the relation_open() -> table_open() change. I've made a pass over this again and updated the header comments in functions that now obtain a lock to mention that fact. Also slightly updated commit msg in the patch. -- David Rowley http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
v3-0001-On-demand-locking-of-partitions-during-INSERT-and.patch
Description: Binary data
