pgsql: Account for collation when coercing the output of a SQL function

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Account for collation when coercing the output of a SQL function
Date: 2020-04-14 21:30:46
Message-ID: E1jOT8o-00025q-Ay@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Account for collation when coercing the output of a SQL function.

Commit 913bbd88d overlooked that the result of coerce_to_target_type
might need collation fixups. Per report from Andreas Joseph Krogh.

Discussion: https://postgr.es/m/VisenaEmail.72.37d08ec2b8cb8fb5.17179940cd3@tc7-visena

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/2d59643dbccaf73bc1f90875ea02dcad641379cd

Modified Files
--------------
src/backend/executor/functions.c | 3 +++
src/test/regress/expected/collate.out | 15 ++++++++++++++-
src/test/regress/sql/collate.sql | 8 ++++++++
3 files changed, 25 insertions(+), 1 deletion(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Geoghegan 2020-04-14 21:39:24 pgsql: Remove obsolete "hole in center of page" comment.
Previous Message Andrew Dunstan 2020-04-14 21:02:03 pgsql: Stop requiring an explicit return from perl subroutines