postgresql/contrib/btree_gist/expected
Peter Eisentraut 8c852ba9a4 Allow some exclusion constraints on partitions
Previously we only allowed unique B-tree constraints on partitions
(and only if the constraint included all the partition keys).  But we
could allow exclusion constraints with the same restriction.  We also
require that those columns be compared for equality, not something
like &&.

Author: Paul A. Jungwirth <pj@illuminatedcomputing.com>
Reviewed-by: Ronan Dunklau <ronan.dunklau@aiven.io>
Reviewed-by: Peter Eisentraut <peter@eisentraut.org>
Discussion: https://www.postgresql.org/message-id/flat/ec8b1d9b-502e-d1f8-e909-1bf9dffe6fa5@illuminatedcomputing.com
2023-07-12 09:25:17 +02:00
..
bit.out
bool.out Fix planner to consider matches to boolean columns in extension indexes. 2022-09-02 17:01:51 -04:00
bytea.out
cash.out
char_1.out Fix results of index-only scans on btree_gist char(N) indexes. 2022-01-08 14:54:39 -05:00
char.out Fix results of index-only scans on btree_gist char(N) indexes. 2022-01-08 14:54:39 -05:00
cidr.out
date.out
enum.out
float4.out
float8.out
inet.out Handle mixed returnable and non-returnable columns better in IOS. 2022-01-03 16:12:11 -05:00
init.out
int2.out
int4.out
int8.out
interval.out
macaddr8.out
macaddr.out
not_equal.out
numeric.out
oid.out
partitions.out Allow some exclusion constraints on partitions 2023-07-12 09:25:17 +02:00
text_1.out
text.out
time.out
timestamp.out
timestamptz.out
timetz.out
uuid.out
varbit.out
varchar_1.out
varchar.out