diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2020-01-02 13:48:54 -0500 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2020-01-02 13:48:54 -0500 |
commit | 4d02eb017e3c1268762fd1a10ec3c569515c047d (patch) | |
tree | 33b3e3824a6c5cdeb48b11b604e1bfbda879aa1d /src/backend/access/gist | |
parent | 5815696bc66b3092f6361f53e0394909647042c8 (diff) | |
download | postgresql-4d02eb017e3c1268762fd1a10ec3c569515c047d.tar.gz postgresql-4d02eb017e3c1268762fd1a10ec3c569515c047d.zip |
Fix collation exposed for scalar function in FROM.
One code path in addRangeTableEntryForFunction() neglected to assign
a collation to the tupdesc entry it constructs (which is a bit odd
considering the other path did do so). This didn't matter before commit
5815696bc, because nothing would look at the type data in this tupdesc;
but now it does.
While at it, make sure we assign the correct typmod as well. Most
function expressions don't have a determinate typmod, but some do.
Per buildfarm, which showed failures in non-C collations, a case
I'd not thought to test for this patch :-(
Diffstat (limited to 'src/backend/access/gist')
0 files changed, 0 insertions, 0 deletions