Re: BUG #14341: insert on conflict (key_column) cann't used with partition table.
| От | Tom Lane |
|---|---|
| Тема | Re: BUG #14341: insert on conflict (key_column) cann't used with partition table. |
| Дата | |
| Msg-id | 27411.1474981474@sss.pgh.pa.us обсуждение |
| Ответ на | BUG #14341: insert on conflict (key_column) cann't used with partition table. (digoal@126.com) |
| Ответы |
Re: BUG #14341: insert on conflict (key_column) cann't
used with partition table.
|
| Список | 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 по дате отправления: