From eb85fabed31d7c3a8fa1396ddfd2ea733c5c8baf Mon Sep 17 00:00:00 2001 From: Justin Pryzby Date: Sun, 10 May 2020 17:30:14 -0500 Subject: [PATCH v5 2/5] Remove mention of double timestamps.. ..which were removed in v10. This was previously discussed here: https://www.postgresql.org/message-id/20191230074721.GM12890%40telsasoft.com --- src/backend/utils/adt/selfuncs.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/backend/utils/adt/selfuncs.c b/src/backend/utils/adt/selfuncs.c index 0f02f32ffd..be08eb4814 100644 --- a/src/backend/utils/adt/selfuncs.c +++ b/src/backend/utils/adt/selfuncs.c @@ -4018,8 +4018,8 @@ estimate_multivariate_ndistinct(PlannerInfo *root, RelOptInfo *rel, * to be treated separately. * * The several datatypes representing absolute times are all converted - * to Timestamp, which is actually a double, and then we just use that - * double value. Note this will give correct results even for the "special" + * to Timestamp, which is actually an int64, and then we promote that to + * a double. Note this will give correct results even for the "special" * values of Timestamp, since those are chosen to compare correctly; * see timestamp_cmp. * -- 2.17.0