aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistutil.c
diff options
context:
space:
mode:
authorTomas Vondra <tomas.vondra@postgresql.org>2019-07-18 12:28:16 +0200
committerTomas Vondra <tomas.vondra@postgresql.org>2019-07-20 16:35:15 +0200
commit5a8ee9f2dbe040b9a0cb7f73a4376633f93b4ab4 (patch)
tree227540c55a492c25bcd6241b9ed83bd96c846553 /src/backend/access/gist/gistutil.c
parentfc4faea17971a927daf936a4b17564140ee412f6 (diff)
downloadpostgresql-5a8ee9f2dbe040b9a0cb7f73a4376633f93b4ab4.tar.gz
postgresql-5a8ee9f2dbe040b9a0cb7f73a4376633f93b4ab4.zip
Use column collation for extended statistics
The current extended statistics code was a bit confused which collation to use. When building the statistics, the collations defined as default for the data types were used (since commit 5e0928005). The MCV code was however using the column collations for MCV serialization, and then DEFAULT_COLLATION_OID when computing estimates. So overall the code was using all three possible options, inconsistently. This uses the column colation everywhere - this makes it consistent with what 5e0928005 did for regular stats. We however do not track the collations in a catalog, because we can derive them from column-level information. This may need to change in the future, e.g. after allowing statistics on expressions. Reviewed-by: Tom Lane Discussion: https://postgr.es/m/8736jdhbhc.fsf%40ansel.ydns.eu Backpatch-to: 12
Diffstat (limited to 'src/backend/access/gist/gistutil.c')
0 files changed, 0 insertions, 0 deletions