From: | Daniel WM <dwilches(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #16293: postgres segfaults and returns SQLSTATE 08006 |
Date: | 2020-03-14 20:43:32 |
Message-ID: | CAEbtaO39qxx7GX=u8j02y5K2eyVGT8gyCOLHS2KNENQS=w_D7Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Hello,
I have finally isolated the issue and I have a set of steps that reliably
cause the segfault:
CREATE TABLE parent_table (
custdob timestamp with time zone not null,
closed BOOLEAN NOT NULL DEFAULT FALSE
) PARTITION BY RANGE (custdob);
CREATE TABLE default_partition (
custdob timestamp with time zone not null,
CONSTRAINT dummy_check CHECK (custdob < '2019-08-02T00:00Z')
);
-- This is needed for the crash, if I add this column when creating the
table "default_partition" then I don't get the crash, but when it's added
with an "ALTER TABLE" then I get the crash.
ALTER TABLE default_partition ADD COLUMN closed BOOLEAN NOT NULL DEFAULT
FALSE;
ALTER TABLE parent_table ATTACH PARTITION default_partition DEFAULT;
INSERT INTO parent_table VALUES ('2020-02-02 01:00:00+00:00', 'f');
--
Daniel Wilches
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2020-03-14 21:21:04 | Re: BUG #16293: postgres segfaults and returns SQLSTATE 08006 |
Previous Message | Tom Lane | 2020-03-14 15:03:05 | Re: BUG #16302: too many range table entries - when count partition table(65538 childs) |