Received: from femail26.sdc1.sfba.home.com (femail26.sdc1.sfba.home.com [24.254.60.16]) by postgresql.org (8.11.3/8.11.4) with ESMTP id f8OBggh28230 for ; Mon, 24 Sep 2001 07:42:42 -0400 (EDT) (envelope-from kway@overtone.org) Received: from bean.overtone.org ([24.249.254.100]) by femail26.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with ESMTP id <20010924114238.CVDT2015.femail26.sdc1.sfba.home.com@bean.overtone.org>; Mon, 24 Sep 2001 04:42:38 -0700 Received: by bean.overtone.org (Postfix, from userid 1001) id A043A5B4B8; Mon, 24 Sep 2001 11:42:33 +0000 (GMT) Date: Mon, 24 Sep 2001 11:42:33 +0000 From: Kevin Way To: Kovacs Baldvin Cc: pgsql-sql@postgresql.org Subject: Re: Server crash caused by CHECK on child Message-ID: <20010924114233.A76269@bean.overtone.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from kb136@hszk.bme.hu on Mon, Sep 24, 2001 at 10:01:43AM +0200 X-Archive-Number: 200109/206 X-Sequence-Number: 4888 > -- 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. Oooh, my bad. I should run your scripts before assuming I know how they fail. > -- However, for you without time to analyzing Kevin's huge > -- scheme, here is the very simplified, crash-causing script. Thank you so much for finding this simplified method of crashing Postgres. Hopefully somebody can find a fix now. > -- 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. That's my problem as well, though your example is vastly easier to trace than mine. -Kevin Way