mirror of
https://github.com/postgres/postgres.git
synced 2025-10-29 22:49:41 +03:00
d92b1cdbab
This reverts commit 9f984ba6d2.
It was making the buildfarm unhappy, apparently setting client_min_messages
in a regression test produces different output if log_statement='all'.
Another issue is that I now suspect the bit sortsupport function was in
fact not correct to call byteacmp(). Revert to investigate both of those
issues.
38 lines
988 B
SQL
38 lines
988 B
SQL
-- float4 check
|
|
|
|
CREATE TABLE float4tmp (a float4);
|
|
|
|
\copy float4tmp from 'data/float4.data'
|
|
|
|
SET enable_seqscan=on;
|
|
|
|
SELECT count(*) FROM float4tmp WHERE a < -179.0;
|
|
|
|
SELECT count(*) FROM float4tmp WHERE a <= -179.0;
|
|
|
|
SELECT count(*) FROM float4tmp WHERE a = -179.0;
|
|
|
|
SELECT count(*) FROM float4tmp WHERE a >= -179.0;
|
|
|
|
SELECT count(*) FROM float4tmp WHERE a > -179.0;
|
|
|
|
SELECT a, a <-> '-179.0' FROM float4tmp ORDER BY a <-> '-179.0' LIMIT 3;
|
|
|
|
CREATE INDEX float4idx ON float4tmp USING gist ( a );
|
|
|
|
SET enable_seqscan=off;
|
|
|
|
SELECT count(*) FROM float4tmp WHERE a < -179.0::float4;
|
|
|
|
SELECT count(*) FROM float4tmp WHERE a <= -179.0::float4;
|
|
|
|
SELECT count(*) FROM float4tmp WHERE a = -179.0::float4;
|
|
|
|
SELECT count(*) FROM float4tmp WHERE a >= -179.0::float4;
|
|
|
|
SELECT count(*) FROM float4tmp WHERE a > -179.0::float4;
|
|
|
|
EXPLAIN (COSTS OFF)
|
|
SELECT a, a <-> '-179.0' FROM float4tmp ORDER BY a <-> '-179.0' LIMIT 3;
|
|
SELECT a, a <-> '-179.0' FROM float4tmp ORDER BY a <-> '-179.0' LIMIT 3;
|