On Sat, Jun 3, 2017 at 10:39 PM, Thomas Munro <thomas.mu...@enterprisedb.com> wrote: > In the meantime, it seems like you agree that rejecting wCTEs that > affect tables with triggers with transition tables is the best > response to this bug report? Do you think that parse analysis is the > right time to do the check? Here's a first attempt at that.
I'm starting to like the approach of reverting the entire transition tables patch. Failing to consider the possibility of a plan with multiple ModifyTable nodes seems like a pretty fundamental design mistake, and I'm not eager either to ship this with that broken or try to fix it at this stage of the release cycle. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
