Re: BUG #14341: insert on conflict (key_column) cann't used with partition table.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: digoal(at)126(dot)com
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #14341: insert on conflict (key_column) cann't used with partition table.
Date: 2016-09-27 13:04:34
Message-ID: 27411.1474981474@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

digoal(at)126(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message amitraj 2016-09-27 13:15:37 BUG #14342: Please restore pgdg-redhat92-9.2-7.noarch.rpm
Previous Message digoal 2016-09-27 12:19:14 BUG #14341: insert on conflict (key_column) cann't used with partition table.