Re: pg_trigger.tgparentid
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Pg Hackers <pgsql-hackers@lists.postgresql.org>,
Amit Langote <amitlangote09@gmail.com>
Date: 2020-02-17T21:59:38Z
Lists: pgsql-hackers
Alvaro Herrera <alvherre@2ndquadrant.com> writes: > As mentioned in https://postgr.es/m/20191231194759.GA24692@alvherre.pgsql > I propose to add a new column to pg_trigger, which allows us to remove a > pg_depend scan when cloning triggers when adding/attaching partitions. > (It's not that I think the scan is a performance problem, but rather > than notionally we try not to depend on pg_depend contents for this kind > of semantic derivation.) It'd be nice if the term "parent trigger" were defined somewhere in this. Seems all right otherwise. regards, tom lane
Commits
-
Record parents of triggers
- b9b408c48724 13.0 landed
-
Fix docs regarding AFTER triggers on partitioned tables
- 902f40dc774b 12.3 landed
- 3acfe6b089a5 13.0 landed
- 143152439dc9 11.8 landed