On 2016-12-07 12:42, Amit Langote wrote:

0001-Catalog-and-DDL-for-partitioned-tables-20.patch
0002-psql-and-pg_dump-support-for-partitioned-tables-20.patch
0003-Catalog-and-DDL-for-partitions-20.patch
0004-psql-and-pg_dump-support-for-partitions-20.patch
0005-Teach-a-few-places-to-use-partition-check-quals-20.patch
0006-Tuple-routing-for-partitioned-tables-20.patch
0007-Update-DDL-Partitioning-chapter-to-reflect-new-devel-20.patch

Patches apply, compile, check OK.


But this yields a segfault:

begin;
create schema if not exists s;
create table s.t (c text, d text, id serial) partition by list ((ascii(substring(coalesce(c, d, ''), 1, 1))));
create table s.t_part_ascii_065 partition of s.t for values in ( 65 );




it logs as follows:

2016-12-07 17:03:45.787 CET 6125 LOG: server process (PID 11503) was terminated by signal 11: Segmentation fault 2016-12-07 17:03:45.787 CET 6125 DETAIL: Failed process was running: create table s.t_part_ascii_065 partition of s.t for values in ( 65 ); 2016-12-07 17:03:45.787 CET 6125 LOG: terminating any other active server processes 2016-12-07 17:03:45.791 CET 6125 LOG: all server processes terminated; reinitializing 2016-12-07 17:03:45.999 CET 11655 LOG: database system was interrupted; last known up at 2016-12-07 17:00:38 CET 2016-12-07 17:03:48.040 CET 11655 LOG: database system was not properly shut down; automatic recovery in progress
2016-12-07 17:03:48.156 CET 11655 LOG:  redo starts at 0/2897988
2016-12-07 17:03:48.172 CET 11655 LOG: invalid magic number 0000 in log segment 000000010000000000000002, offset 9207808
2016-12-07 17:03:48.172 CET 11655 LOG:  redo done at 0/28C72C0
2016-12-07 17:03:48.172 CET 11655 LOG: last completed transaction was at log time 2016-12-07 17:01:29.580562+01 2016-12-07 17:03:49.534 CET 11655 LOG: MultiXact member wraparound protections are now enabled 2016-12-07 17:03:49.622 CET 6125 LOG: database system is ready to accept connections



Thanks,

Erik Rijkers


--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Reply via email to