Re: [HACKERS] Adding support for Default partition in partitioning
От | Rajkumar Raghuwanshi |
---|---|
Тема | Re: [HACKERS] Adding support for Default partition in partitioning |
Дата | |
Msg-id | CAKcux6neHEasAeJuHiLiUYMWxQ8C0VxtjAxETggZS1CvxaSACg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [HACKERS] Adding support for Default partition in partitioning (Jeevan Ladhe <jeevan.ladhe@enterprisedb.com>) |
Ответы |
Re: [HACKERS] Adding support for Default partition in partitioning
|
Список | pgsql-hackers |
On Wed, Sep 6, 2017 at 5:25 PM, Jeevan Ladhe <jeevan.ladhe@enterprisedb.com> wrote:
Hi,Attached is the rebased set of patches.Robert has committed[1] patch 0001 in V26 series, hence the patch numberingin V27 is now decreased by 1 for each patch as compared to V26.
Hi,
I have applied v27 patches and while testing got below observation.
Observation: in below partition table, d1 constraints not allowing NULL to be inserted in b column
but I am able to insert it.
steps to reproduce:
create table d0 (a int, b int) partition by range(a,b);
create table d1 partition of d0 for values from (0,0) to (maxvalue,maxvalue);
postgres=# insert into d0 values (0,null);
INSERT 0 1
postgres=# \d+ d1
Table "public.d1"
Column | Type | Collation | Nullable | Default | Storage | Stats target | Description
--------+---------+-----------+----------+---------+---------+--------------+-------------
a | integer | | | | plain | |
b | integer | | | | plain | |
Partition of: d0 FOR VALUES FROM (0, 0) TO (MAXVALUE, MAXVALUE)
Partition constraint: ((a IS NOT NULL) AND (b IS NOT NULL) AND ((a > 0) OR ((a = 0) AND (b >= 0))))
postgres=# select tableoid::regclass,* from d0;
tableoid | a | b
----------+---+---
d1 | 0 |
(1 row)
Thanks & Regards,
Rajkumar Raghuwanshi
QMG, EnterpriseDB Corporation В списке pgsql-hackers по дате отправления: