Re: FOR EACH ROW triggers on partitioned tables
Alvaro Herrera <alvherre@alvh.no-ip.org>
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Thomas Munro <thomas.munro@enterprisedb.com>, Robert Haas <robertmhaas@gmail.com>, Pg Hackers <pgsql-hackers@postgresql.org>, Simon Riggs <simon@2ndquadrant.com>
Date: 2018-03-22T16:40:23Z
Lists: pgsql-hackers
Peter Eisentraut wrote: > On 3/21/18 19:18, Alvaro Herrera wrote: > > Here's v8, which addresses all your comments except the doc updates. I > > added a few more tests, too. Thanks for the review! I intend to commit > > this shortly, probably not before Friday to give some more time for > > others to review/comment. > > Looks good, does what it needs to do. > > A small fixup attached. In particular, I renamed one trigger from "f", > which created confusing output, looking like a boolean column. Thanks! > This comment in the tests I don't understand: > > -- verify that the FOR UPDATE OF (columns) is propagated correctly > > I don't see how this applies to the tests that follow. Does this have > something to do with the subsequent foreign keys patch perhaps? Not at all ... I meant "AFTER UPDATE OF columns" (used as a firing event). Not sure how I typo'ed it that badly. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Commits
-
Allow FOR EACH ROW triggers on partitioned tables
- 86f575948c77 11.0 landed
-
Fix CommandCounterIncrement in partition-related DDL
- 4dba331cb3dc 11.0 landed
-
Mention trigger name in trigger test
- cef60043dd27 11.0 landed
-
Fix transition tables for partition/inheritance.
- 501ed02cf6f4 10.0 cited