Re: Regression instability + performance issue in TRIGGERS view
Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>, pgsql-hackers@lists.postgresql.org
Date: 2020-04-23T06:53:11Z
Lists: pgsql-hackers
On 2020-04-23 00:27, Tom Lane wrote: > This should not only fix the regression instability but offer a pretty > significant speedup for real-world use of the triggers view, so I > propose squeezing it in even though we're past feature freeze. I think that's fine. > However ... what about the back branches? As noted, we are seeing > this now in the back branches, at least v12. Are we willing to make > a change in the information_schema in back branches to make the > instability go away? (And if not, how else could we fix it?) That would be okay with me. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Commits
-
Repair performance regression in information_schema.triggers view.
- baf17ad9dff4 13.0 landed
- 776f6d3d0464 11.8 landed
- 64e49a67e020 12.3 landed