Please find attached an updated patch with review comments and bugs reported till date implemented.
Hello Rahila,
Tested on "efa2c18 Doc fix: scale(numeric) returns integer, not numeric."
(1) With the new patch, we allow new partitions when there is overlapping data with default partition. The entries in default are ignored when running queries satisfying the new partition.
DROP TABLE list1; CREATE TABLE list1 ( a int, b int ) PARTITION BY LIST (a); CREATE TABLE list1_1 (LIKE list1); ALTER TABLE list1 ATTACH PARTITION list1_1 FOR VALUES IN (1); CREATE TABLE list1_def PARTITION OF list1 DEFAULT; INSERT INTO list1 SELECT generate_series(1,2),1; -- Partition overlapping with DEF CREATE TABLE list1_2 PARTITION OF list1 FOR VALUES IN (2); INSERT INTO list1 SELECT generate_series(2,3),2;
postgres=# SELECT * FROM list1 ORDER BY a,b;
a | b
---+---
1 | 1
2 | 1
2 | 2
3 | 2
(4 rows)
postgres=# SELECT * FROM list1 WHERE a=2;
a | b
---+---
2 | 2
(1 row)
This ignores the a=2 entries in the DEFAULT.
postgres=# SELECT * FROM list1_def;
a | b
---+---
2 | 1
3 | 2
(2 rows)
(2) I get the following warning:
partition.c: In function ‘check_new_partition_bound’:
partition.c:882:15: warning: ‘boundinfo’ may be used uninitialized in this function [-Wmaybe-uninitialized]
&& boundinfo->has_default)
^
preproc.y:3250.2-8: warning: type clash on default action: <str> != <>
>1.
>In following block, we can just do with def_index, and we do not need found_def
>flag. We can check if def_index is -1 or not to decide if defaultpartition is
>present.
found_def is used to set boundinfo->has_default which is used at couple
of other places to check if default partition exists. The implementation is similar
to has_null.
>3.
>In following function isDefaultPartitionBound, first statement "return false"
>is not needed.
It is needed to return false if the node is not DefElem.
