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: Amit Langote <amitlangote09@gmail.com>,
Pg Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2020-02-27T16:32:21Z
Lists: pgsql-hackers
Alvaro Herrera <alvherre@2ndquadrant.com> writes: > Thanks both -- pushed. I also changed regress/sql/triggers to leave > tables around that have a non-zero tgparentid. This ensures that the > pg_upgrade test sees such objects, as well as findoidjoins. > I refrained from doing the findoidjoins dance itself, though; I got a > large number of false positives that I think are caused by some pg12-era > hacking. Generally I try to update findoidjoins once per release cycle, after feature freeze. I don't think it's worth messing with it more often than that. But thanks for making sure there'll be data for it to find. 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