Server crash(failed assertion) when two "insert" in one SQL: Step to reproduce: create table t(a int, b int) partition by range(a); create table t_p1 partition of t for values from (1) to (100); create table t_p2 partition of t for values from (100) to (200); create table t_p3 partition of t for values from (200) to (300);
create table b(a int, b int); with a(a,b) as(insert into t values(3, 3) returning a, b) insert into b select * from a; Please check it. 2017-01-04 14:11 GMT+08:00 Rajkumar Raghuwanshi < rajkumar.raghuwan...@enterprisedb.com>: > On Wed, Jan 4, 2017 at 10:37 AM, Amit Langote < > langote_amit...@lab.ntt.co.jp> wrote: > >> On 2017/01/03 19:04, Rajkumar Raghuwanshi wrote: >> > On Tue, Dec 27, 2016 at 3:24 PM, Amit Langote wrote: >> >> >> >> Attached patch should fix the same. >> > >> > I have applied attached patch, server crash for range is fixed, but >> still >> > getting crash for multi-level list partitioning insert. >> > >> > postgres=# CREATE TABLE test_ml_l (a int, b int, c varchar) PARTITION BY >> > LIST(c); >> >> [ ... ] >> >> > postgres=# INSERT INTO test_ml_l SELECT i, i, to_char(i/50, 'FM0000') >> FROM >> > generate_series(0, 599, 2) i; >> > 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. >> >> Hm, that's odd. I tried your new example, but didn't get the crash. >> >> Thanks, >> Amit >> > > Thanks, I have pulled latest sources from git, and then applied patch > "fix-wrong-ecxt_scantuple-crash.patch", Not getting crash now, may be I > have missed something last time. > > -- GaoZengqi pgf...@gmail.com zengqi...@gmail.com
