On Thu, May 11, 2017 at 7:54 AM, Amit Kapila <amit.kapil...@gmail.com> wrote: > Few comments: > 1. > Operating directly on partition doesn't allow update to move row. > Refer below example: > create table t1(c1 int) partition by range(c1); > create table t1_part_1 partition of t1 for values from (1) to (100); > create table t1_part_2 partition of t1 for values from (100) to (200); > insert into t1 values(generate_series(1,11)); > insert into t1 values(generate_series(110,120)); > > postgres=# update t1_part_1 set c1=122 where c1=11; > ERROR: new row for relation "t1_part_1" violates partition constraint > DETAIL: Failing row contains (122).
I think that's correct behavior. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
