Re: [HACKERS] Default Partition for Range - Mailing list pgsql-hackers

From Dilip Kumar
Subject Re: [HACKERS] Default Partition for Range
Date
Msg-id CAFiTN-tDSPh9Fa_uzfrxg=nO+ZFY+HVX0Vx643nYAHXysEdukw@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Default Partition for Range  (Beena Emerson <memissemerson@gmail.com>)
Responses Re: [HACKERS] Default Partition for Range  (Dilip Kumar <dilipbalaut@gmail.com>)
List pgsql-hackers
On Thu, Jun 15, 2017 at 11:20 AM, Beena Emerson <memissemerson@gmail.com> wrote:
> Hello,
>
> PFA the updated patch.
> This is rebased over v21 patches of list partition.
> (http://www.mail-archive.com/pgsql-hackers@postgresql.org/msg316818.html)

While testing I have noticed segmentation fault for a simple case.

create table test(a int, b int) partition by range(a,b);
create table test1 partition of test DEFAULT;
postgres=# drop table test1;
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.

This is basically crashing in RelationBuildPartitionDesc, so I think
we don't have any test case for testing DEFAULT range partition where
partition key has more than one attribute.  So I suggest we can add
such test case.


-- 
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: [HACKERS] Getting server crash on Windows when using ICU collation
Next
From: Sergey Burladyan
Date:
Subject: Re: [HACKERS] Broken hint bits (freeze)