From: Tom Lane <tgl@sss.pgh.pa.us>
To: Christoph Berg <christoph.berg@credativ.de>
Cc: PostgreSQL Bugs <pgsql-bugs@postgresql.org>
Subject: Re: Fallout from 'Make type "name" collation-aware' and tg_table_name
Date: Wed, 08 Jun 2022 10:05:59 -0400
Message-ID: <1615599.1654697159@sss.pgh.pa.us> (raw)
In-Reply-To: <YqCfLapinj6+mJ6i@msg.credativ.de>
References: <YqCfLapinj6+mJ6i@msg.credativ.de>
Christoph Berg <christoph.berg@credativ.de> writes:
> I was just debugging a client problem where a trigger was running fine
> with PG 11, but very slow with PG 13.
Hmmm ... I do not see how the collation within the PERFORM statement
would affect whatever it's calling?
regards, tom lane
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-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, christoph.berg@credativ.de
Subject: Re: Fallout from 'Make type "name" collation-aware' and tg_table_name
In-Reply-To: <1615599.1654697159@sss.pgh.pa.us>
* 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