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-28 12:37:41
Message-ID: 14494.1475066261@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

=?GBK?B?tcK45w==?= <digoal(at)126(dot)com> writes:
> At 2016-09-27 21:04:34, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Can't reproduce that on the basis of the given information.

> $ git clone https://github.com/postgrespro/pg_pathman
> ...

If it requires pathman, and apparently not even the default settings for
that, I'd say this is a pathman bug. It looks a bit like the partitions
are getting processed despite the plan claiming they aren't.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message huang 2016-09-28 13:46:22 vacuumdb parallel has a deadlock detected in 9.5.4
Previous Message Devrim Gündüz 2016-09-28 10:31:13 Re: BUG #14342: Please restore pgdg-redhat92-9.2-7.noarch.rpm