Re: Fallout from 'Make type "name" collation-aware' and tg_table_name

Re: Tom Lane
> Christoph Berg <christoph(dot)berg(at)credativ(dot)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?

Here's the actual reproducer I used:

$ cat run.sql
drop database if exists test;
create database test;
\c test

\i pgdump
reset all;

alter system set log_line_prefix = '%m [%p] %q%u(at)%d %a ';
select pg_reload_conf();

set jit=off;
LOAD 'auto_explain';
set auto_explain.log_analyze=on;
set auto_explain.log_buffers=on;
set auto_explain.log_min_duration=0;
set auto_explain.log_nested_statements=on;
set auto_explain.log_triggers=on;

set application_name = 'collate_bug';
INSERT INTO public.identity_provider (id, created, lastmodified, "version", identity_zone_id, "name", origin_key, "type", config, active)
VALUES('24e9dd6d-5a63-9ea8-b425-ae89aa419a33', CURRENT_TIMESTAMP,CURRENT_TIMESTAMP, 0, 'insert-test', 'test', 'test', 'test', 'none', true);

Mit freundlichen Grüßen,
Christoph Berg
--
Senior Consultant, Tel.: +49 2166 9901 187
credativ GmbH, HRB Mönchengladbach 12080, USt-ID-Nummer: DE204566209
Trompeterallee 108, 41189 Mönchengladbach
Geschäftsführung: Dr. Michael Meskes, Geoff Richardson, Peter Lilley
Unser Umgang mit personenbezogenen Daten unterliegt folgenden
Bestimmungen: https://www.credativ.de/datenschutz