Received: from ural2.hszk.bme.hu (ural2.hszk.bme.hu [152.66.130.2]) by postgresql.org (8.11.3/8.11.4) with ESMTP id f8O81oh89889; Mon, 24 Sep 2001 04:01:51 -0400 (EDT) (envelope-from kb136@hszk.bme.hu) Received: (from kb136@localhost) by ural2.hszk.bme.hu (8.11.3/8.11.3) id f8O81hv07521; Mon, 24 Sep 2001 10:01:43 +0200 (MEST) Date: Mon, 24 Sep 2001 10:01:43 +0200 (MEST) From: Kovacs Baldvin X-X-Sender: To: , , Kevin Way Subject: Server crash caused by CHECK on child Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archive-Number: 200109/629 X-Sequence-Number: 13508 -- 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 --