From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: Copy collencoding in CREATE COLLATION / FROM |
Date: | 2017-06-30 12:55:21 |
Message-ID: | E1dQvSD-0007S9-Td@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Copy collencoding in CREATE COLLATION / FROM
This command used to compute the collencoding entry like when a
completely new collation is created. But for example when copying the
"C" collation, this would then result in a collation that has a
collencoding entry for the current database encoding rather than -1,
thus not making an exact copy. This has probably no practical impact,
but making this change keeps the catalog contents neat.
Reported-by: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/54baa48139ae6b67347bea6a9183d494e625939b
Modified Files
--------------
src/backend/commands/collationcmds.c | 16 ++++++++++------
1 file changed, 10 insertions(+), 6 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2017-06-30 14:02:04 | pgsql: Add missing period to comment. |
Previous Message | Tom Lane | 2017-06-29 02:11:17 | pgsql: Eat XIDs more efficiently in recovery TAP test. |