Subject: Re: Regression instability + performance issue in TRIGGERS view
To: Tom Lane <tgl@sss.pgh.pa.us>, pgsql-hackers@lists.postgresql.org
References: <5891.1587594470@sss.pgh.pa.us>
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Organization: 2ndQuadrant
Message-ID: <7c829b06-808c-3570-8738-70596f370601@2ndquadrant.com>
Date: Thu, 23 Apr 2020 08:53:11 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:52.0)
 Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <5891.1587594470@sss.pgh.pa.us>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk

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