mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-07-13 23:29:17 +02:00
fedc97cdfd
Up to now, get_const_expr() insisted on prefixing BIT and VARBIT
literals with 'B'. That's not really necessary, because we always
append explicit-cast syntax to identify the constant's type.
Moreover, it's subtly wrong for VARBIT, because the parser will
interpret B'...' as '...'::"bit"; see make_const() which explicitly
assigns type BITOID for a T_BitString literal. So what had been
a simple VARBIT literal is reconstructed as ('...'::"bit")::varbit,
which is not the same thing, at least not before constant folding.
This results in odd differences after dump/restore, as complained
of by the patch submitter, and it could result in actual failures in
partitioning or inheritance DDL operations (see commit 542320c2b,
which repaired similar misbehaviors for some other data types).
Fixing it is pretty easy: just remove the special case and let the
default code path handle these types. We could have kept the special
case for BIT only, but there seems little point in that.
Like the previous patch, I judge that back-patching this into stable
branches wouldn't be a good idea. However, it seems not quite too
late for v11, so let's fix it there.
Paul Guo, reviewed by Davy Machado and John Naylor, minor adjustments
by me
Discussion: https://postgr.es/m/CABQrizdTra=2JEqA6+Ms1D1k1Kqw+aiBBhC9TreuZRX2JzxLAA@mail.gmail.com
77 lines
1.5 KiB
Plaintext
77 lines
1.5 KiB
Plaintext
-- varbit check
|
|
CREATE TABLE varbittmp (a varbit);
|
|
\copy varbittmp from 'data/varbit.data'
|
|
SET enable_seqscan=on;
|
|
SELECT count(*) FROM varbittmp WHERE a < '1110100111010';
|
|
count
|
|
-------
|
|
549
|
|
(1 row)
|
|
|
|
SELECT count(*) FROM varbittmp WHERE a <= '1110100111010';
|
|
count
|
|
-------
|
|
550
|
|
(1 row)
|
|
|
|
SELECT count(*) FROM varbittmp WHERE a = '1110100111010';
|
|
count
|
|
-------
|
|
1
|
|
(1 row)
|
|
|
|
SELECT count(*) FROM varbittmp WHERE a >= '1110100111010';
|
|
count
|
|
-------
|
|
51
|
|
(1 row)
|
|
|
|
SELECT count(*) FROM varbittmp WHERE a > '1110100111010';
|
|
count
|
|
-------
|
|
50
|
|
(1 row)
|
|
|
|
CREATE INDEX varbitidx ON varbittmp USING GIST ( a );
|
|
SET enable_seqscan=off;
|
|
SELECT count(*) FROM varbittmp WHERE a < '1110100111010'::varbit;
|
|
count
|
|
-------
|
|
549
|
|
(1 row)
|
|
|
|
SELECT count(*) FROM varbittmp WHERE a <= '1110100111010'::varbit;
|
|
count
|
|
-------
|
|
550
|
|
(1 row)
|
|
|
|
SELECT count(*) FROM varbittmp WHERE a = '1110100111010'::varbit;
|
|
count
|
|
-------
|
|
1
|
|
(1 row)
|
|
|
|
SELECT count(*) FROM varbittmp WHERE a >= '1110100111010'::varbit;
|
|
count
|
|
-------
|
|
51
|
|
(1 row)
|
|
|
|
SELECT count(*) FROM varbittmp WHERE a > '1110100111010'::varbit;
|
|
count
|
|
-------
|
|
50
|
|
(1 row)
|
|
|
|
-- Test index-only scans
|
|
SET enable_bitmapscan=off;
|
|
EXPLAIN (COSTS OFF)
|
|
SELECT a FROM bittmp WHERE a BETWEEN '1000000' and '1000001';
|
|
QUERY PLAN
|
|
---------------------------------------------------------------------
|
|
Index Only Scan using bitidx on bittmp
|
|
Index Cond: ((a >= '1000000'::"bit") AND (a <= '1000001'::"bit"))
|
|
(2 rows)
|
|
|