| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Regression instability + performance issue in TRIGGERS view |
| Date: | 2020-04-23 06:53:11 |
| Message-ID: | 7c829b06-808c-3570-8738-70596f370601@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | 曾文旌 | 2020-04-23 07:10:31 | Re: [Proposal] Global temporary tables |
| Previous Message | Peter Eisentraut | 2020-04-23 06:46:50 | Re: WAL usage calculation patch |