postgresql/contrib/btree_gist/expected/int2.out
Tom Lane 542320c2bd Be more careful about printing constants in ruleutils.c.
The previous coding in get_const_expr() tried to avoid quoting integer,
float, and numeric literals if at all possible.  While that looks nice,
it means that dumped expressions might re-parse to something that's
semantically equivalent but not the exact same parsetree; for example
a FLOAT8 constant would re-parse as a NUMERIC constant with a cast to
FLOAT8.  Though the result would be the same after constant-folding,
this is problematic in certain contexts.  In particular, Jeff Davis
pointed out that this could cause unexpected failures in ALTER INHERIT
operations because of child tables having not-exactly-equivalent CHECK
expressions.  Therefore, favor correctness over legibility and dump
such constants in quotes except in the limited cases where they'll
be interpreted as the same type even without any casting.

This results in assorted small changes in the regression test outputs,
and will affect display of user-defined views and rules similarly.
The odds of that causing problems in the field seem non-negligible;
given the lack of previous complaints, it seems best not to change
this in the back branches.
2015-03-30 14:59:49 -04:00

92 lines
1.5 KiB
Plaintext

-- int2 check
CREATE TABLE int2tmp (a int2);
\copy int2tmp from 'data/int2.data'
SET enable_seqscan=on;
SELECT count(*) FROM int2tmp WHERE a < 237;
count
-------
297
(1 row)
SELECT count(*) FROM int2tmp WHERE a <= 237;
count
-------
298
(1 row)
SELECT count(*) FROM int2tmp WHERE a = 237;
count
-------
1
(1 row)
SELECT count(*) FROM int2tmp WHERE a >= 237;
count
-------
249
(1 row)
SELECT count(*) FROM int2tmp WHERE a > 237;
count
-------
248
(1 row)
SELECT a, a <-> '237' FROM int2tmp ORDER BY a <-> '237' LIMIT 3;
a | ?column?
-----+----------
237 | 0
232 | 5
228 | 9
(3 rows)
CREATE INDEX int2idx ON int2tmp USING gist ( a );
SET enable_seqscan=off;
SELECT count(*) FROM int2tmp WHERE a < 237::int2;
count
-------
297
(1 row)
SELECT count(*) FROM int2tmp WHERE a <= 237::int2;
count
-------
298
(1 row)
SELECT count(*) FROM int2tmp WHERE a = 237::int2;
count
-------
1
(1 row)
SELECT count(*) FROM int2tmp WHERE a >= 237::int2;
count
-------
249
(1 row)
SELECT count(*) FROM int2tmp WHERE a > 237::int2;
count
-------
248
(1 row)
EXPLAIN (COSTS OFF)
SELECT a, a <-> '237' FROM int2tmp ORDER BY a <-> '237' LIMIT 3;
QUERY PLAN
------------------------------------------------
Limit
-> Index Only Scan using int2idx on int2tmp
Order By: (a <-> '237'::smallint)
(3 rows)
SELECT a, a <-> '237' FROM int2tmp ORDER BY a <-> '237' LIMIT 3;
a | ?column?
-----+----------
237 | 0
232 | 5
228 | 9
(3 rows)