Tom Lane <t...@sss.pgh.pa.us> writes: > So I don't think that the mere fact of being an ANY trigger rather than > a command-specific trigger should be taken to mean that a particular > ordering is desirable. Trigger name order isn't the greatest solution > by any means, but it's more flexible than hard-wiring according to > trigger type.
That ANY sandwich idea is then dead, I will fix it tomorrow to rather just handle a single list of BEFORE and AFTER triggers (that's 2 lists total) ordered by trigger name. v19 will also integrate latest doc comments from Thom and most from Andres, I don't know how to fix the plpython specifics he's talking about. About the reviewing and the commit fest closing, even if that patch is big it's a principled implementation: the integration of the facility is done in the same way in lots of different places, and is not rocket science either (we removed all the complexity). So I guess it's not really an herculean job here, just a certain amount of mechanical edits: we just support too many commands ;) Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
