From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: pgsql-hackers@lists.postgresql.org
Subject: Re: Regression instability + performance issue in TRIGGERS view
Date: Thu, 23 Apr 2020 08:53:11 +0200
Message-ID: <7c829b06-808c-3570-8738-70596f370601@2ndquadrant.com> (raw)
In-Reply-To: <5891.1587594470@sss.pgh.pa.us>
References: <5891.1587594470@sss.pgh.pa.us>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: peter.eisentraut@2ndquadrant.com, tgl@sss.pgh.pa.us, pgsql-hackers@lists.postgresql.org
Subject: Re: Regression instability + performance issue in TRIGGERS view
In-Reply-To: <7c829b06-808c-3570-8738-70596f370601@2ndquadrant.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox