From: Kovacs Baldvin <kb136@hszk.bme.hu>
To: pgsql-hackers@postgresql.org
To: pgsql-sql@postgresql.org
To: Kevin Way <kevin.way@overtone.org>
Subject: Server crash caused by CHECK on child
Date: Mon, 24 Sep 2001 10:01:43 +0200 (MEST)
Message-ID: <Pine.GSO.4.33.0109241000560.5647-100000@ural2> (raw)
-- Hi Kevin, and everyone!
--
-- I don't think that I only found a minor bug compared to
-- the other you wrote in your last letter: the backend crash
-- is caused by the same CHECK constraint in the child table.
--
-- However, for you without time to analyzing Kevin's huge
-- scheme, here is the very simplified, crash-causing script.
--
------------------------------------
drop table child;
drop table ancestor;
create table ancestor (
node_id int4,
a int4
);
create table child (
b int4 NOT NULL DEFAULT 0 ,
c int4 not null default 3,
CHECK ( child.b = 0 OR child.b = 1 )
) inherits (ancestor);
insert into ancestor values (3,4);
insert into child (node_id, a, b) values (5,6,1);
update ancestor set a=8 where node_id=5;
---------------------------------
--
-- I am hunting it, but I have to learn all what this query-executing
-- about, so probably it takes uncomparable longer for me than for
-- a developer.
--
-- Regards,
-- Baldvin
--
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: kb136@hszk.bme.hu, pgsql-hackers@postgresql.org, kevin.way@overtone.org
Subject: Re: Server crash caused by CHECK on child
In-Reply-To: <Pine.GSO.4.33.0109241000560.5647-100000@ural2>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox