From: | Dilip Kumar <dilipbalaut(at)gmail(dot)com> |
---|---|
To: | amul sul <sulamul(at)gmail(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>, Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp>, David Steele <david(at)pgmasters(dot)net>, Greg Stark <stark(at)mit(dot)edu>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [POC] hash partitioning |
Date: | 2017-05-15 15:36:35 |
Message-ID: | CAFiTN-tXrYjGPo4hK8c-KWnweSw=JT=WShcyjAboof_T7-J3MA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, May 15, 2017 at 4:27 PM, amul sul <sulamul(at)gmail(dot)com> wrote:
> Updated patches attached.
While testing latest patch I found a strange behaviour.
test1:
postgres=# create table x (a int) partition by hash(a);
CREATE TABLE
postgres=# create table x1 partition of x for values with (modulus 4,
remainder 0);
CREATE TABLE
postgres=# create table x2 partition of x for values with (modulus 4,
remainder 1);
CREATE TABLE
postgres=# insert into x values(1);
2017-05-15 20:55:20.446 IST [28045] ERROR: no partition of relation
"x" found for row
2017-05-15 20:55:20.446 IST [28045] DETAIL: Partition key of the
failing row contains (a) = (1).
2017-05-15 20:55:20.446 IST [28045] STATEMENT: insert into x values(1);
ERROR: no partition of relation "x" found for row
DETAIL: Partition key of the failing row contains (a) = (1).
Test2:
postgres=# insert into x2 values(100); -- it should violates
partition constraint
INSERT 0 1
Seems like a bug or am I missing something completely?
--
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Sokolov Yura | 2017-05-15 15:40:12 | Re: Small improvement to compactify_tuples |
Previous Message | David Fetter | 2017-05-15 15:34:18 | Re: Hash Functions |