Received: from femail43.sdc1.sfba.home.com (femail43.sdc1.sfba.home.com [24.254.60.37]) by postgresql.org (8.11.3/8.11.4) with ESMTP id f8OGBqh05877 for ; Mon, 24 Sep 2001 12:11:52 -0400 (EDT) (envelope-from kway@overtone.org) Received: from bean.overtone.org ([24.249.254.100]) by femail43.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with ESMTP id <20010924161150.KRQY10023.femail43.sdc1.sfba.home.com@bean.overtone.org>; Mon, 24 Sep 2001 09:11:50 -0700 Received: by bean.overtone.org (Postfix, from userid 1001) id C99D75B4B8; Mon, 24 Sep 2001 16:11:48 +0000 (GMT) Date: Mon, 24 Sep 2001 16:11:48 +0000 From: Kevin Way To: Josh Berkus Cc: pgsql-sql@postgresql.org Subject: Re: Bug?: Update on ancestor for a row of a child Message-ID: <20010924161148.A23482@bean.overtone.org> References: <20010924025150.A6840@bean.overtone.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from josh@agliodbs.com on Mon, Sep 24, 2001 at 08:11:59AM -0700 X-Archive-Number: 200109/213 X-Sequence-Number: 4895 > And you think that Oracle is entirely free of bugs? ;-) Yes, but they'd be exciting technology-oriented e-business enabled bugs! > Still, I understand your frustration. Thanks... It's just frustrating that the bug is on something so basic, which makes it both hard to code around and hard for me to delve into the postgres source and fix. I spent a few hours tracing source before finally conceding the point that it takes more than a few hours to understand postgres internals well enough to fix a major bug. For development purposes I've just removed all the CHECK constraints from my child tables, and I'm hoping some genius will solve the problem by the time I'm looking to deploy. -Kevin Way