On 2019/01/24 12:03, Alvaro Herrera wrote:
> On 2019-Jan-24, Amit Langote wrote:
>
>> Fixed in the attached. We don't support inheriting EXCLUSION constraints
>> yet, so no need to consider their indexes.
>
> Looks good, pushed.
Thank you.
Regards,
Amit
On 2019-Jan-24, Amit Langote wrote:
> Fixed in the attached. We don't support inheriting EXCLUSION constraints
> yet, so no need to consider their indexes.
Looks good, pushed.
--
Álvaro Herrerahttps://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Traini
On 2019/01/24 6:10, Alvaro Herrera wrote:
> Hello
>
> On 2019-Jan-23, Amit Langote wrote:
>
>> It seems that ATExecDetachPartition misses to mark a child's primary key
>> constraint entry (if any) as local (conislocal=true, coninhcount=0), which
>> causes this:
>>
>> create table p (a int primary
Hello
On 2019-Jan-23, Amit Langote wrote:
> It seems that ATExecDetachPartition misses to mark a child's primary key
> constraint entry (if any) as local (conislocal=true, coninhcount=0), which
> causes this:
>
> create table p (a int primary key) partition by list (a);
> create table p2 partiti
Hi,
It seems that ATExecDetachPartition misses to mark a child's primary key
constraint entry (if any) as local (conislocal=true, coninhcount=0), which
causes this:
create table p (a int primary key) partition by list (a);
create table p2 partition of p for values in (2);
alter table p detach par
