On Thu, May 25, 2017 at 3:03 PM, Jeevan Ladhe <jeevan.ladhe@enterprisedb.com> wrote: > > Forgot to attach the patch. > PFA. > > On Thu, May 25, 2017 at 3:02 PM, Jeevan Ladhe <jeevan.ladhe@enterprisedb.com> wrote: >> >> Hi Rajkumar, >> >>> postgres=# CREATE TEMP TABLE temp_list_part (a int) PARTITION BY LIST (a); >>> CREATE TABLE >>> postgres=# CREATE TEMP TABLE temp_def_part (a int); >>> CREATE TABLE >>> postgres=# ALTER TABLE temp_list_part ATTACH PARTITION temp_def_part DEFAULT; >>> server closed the connection unexpectedly >>> This probably means the server terminated abnormally >>> before or while processing the request. >>> The connection to the server was lost. Attempting reset: Failed. >>> !> >> >> >> Thanks for reporting. >> PFA patch that fixes above issue. >>
The existing comment is not valid /* * A null partition key is only acceptable if null-accepting list * partition exists. */ as we allow NULL to be stored in default. It should be updated.
DROP TABLE list1; CREATE TABLE list1 ( a int) PARTITION BY LIST (a); CREATE TABLE list1_1 (LIKE list1); ALTER TABLE list1 ATTACH PARTITION list1_1 FOR VALUES IN (2); CREATE TABLE list1_def PARTITION OF list1 DEFAULT; INSERT INTO list1 VALUES (NULL); SELECT * FROM list1_def; a ---
