Re: BUG #14341: insert on conflict (key_column) cann't used with partition table. - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #14341: insert on conflict (key_column) cann't used with partition table.
Date
Msg-id 27411.1474981474@sss.pgh.pa.us
Whole thread Raw
In response to BUG #14341: insert on conflict (key_column) cann't used with partition table.  (digoal@126.com)
Responses Re: BUG #14341: insert on conflict (key_column) cann't used with partition table.  (德哥 <digoal@126.com>)
List pgsql-bugs
digoal@126.com writes:
> postgres=# \d test
>                Table "postgres.test"
>   Column  |            Type             | Modifiers
> ----------+-----------------------------+-----------
>  id       | integer                     | not null
>  info     | text                        |
>  crt_time | timestamp without time zone |
> Indexes:
>     "test_pkey" PRIMARY KEY, btree (id)
> Number of child tables: 100 (Use \d+ to list them.)

> postgres=# insert into test(id,info,crt_time) values(1, md5(random()::text),
> now()) on conflict (id) do update set
> info=excluded.info,crt_time=excluded.crt_time;
> ERROR:  XX000: unexpected failure to find arbiter index
> LOCATION:  ExecCheckIndexConstraints, execIndexing.c:594

Can't reproduce that on the basis of the given information.

            regards, tom lane

pgsql-bugs by date:

Previous
From: digoal@126.com
Date:
Subject: BUG #14341: insert on conflict (key_column) cann't used with partition table.
Next
From: jungle Boogie
Date:
Subject: Re: BUG #14334: vacuumdb.c build failure on openbsd