Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 1D2082E2D67 for ; Mon, 21 Jan 2008 09:50:16 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 86282-06 for ; Mon, 21 Jan 2008 09:50:01 -0400 (AST) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.171]) by postgresql.org (Postfix) with ESMTP id 9B08C2E02EB for ; Mon, 21 Jan 2008 09:50:08 -0400 (AST) Received: from [192.168.146.33] (p50806865.dip.t-dialin.net [80.128.104.101]) by mrelayeu.kundenserver.de (node=mrelayeu3) with ESMTP (Nemesis) id 0MKxQS-1JGx2K37kT-0004xt; Mon, 21 Jan 2008 14:50:06 +0100 Message-ID: <4794A2CA.1000401@deriva.de> Date: Mon, 21 Jan 2008 14:48:58 +0100 From: =?ISO-8859-1?Q?Christian_Schr=F6der?= Organization: Deriva GmbH User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: Tom Lane CC: pgsql-sql@postgresql.org Subject: Re: (possible) bug with constraint exclusion References: <23924.1200081368@sss.pgh.pa.us> <1442.1200115443@sss.pgh.pa.us> In-Reply-To: <1442.1200115443@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Provags-ID: V01U2FsdGVkX18rv0jVOMmNyuRAWAwd1QgnPFXvdaTuLQhp8HC 0CrEfLnlTh+bB8VPv7eQ/UyoFKMDxUvdNCr9axO2HuYRJS0SE0 XTGfICRpIqTXk5YM8pnQQ== X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200801/158 X-Sequence-Number: 30011 Hi list, > It's a bug, it's patched: > http://archives.postgresql.org/pgsql-committers/2008-01/msg00184.php > I have just stumbled on the same bug today and was very happy to find a patch; however, I have a 8.2.6 server running which of course cannot be patched. (According to the CVS tags the revisions of plancat.c and predtest.c in the 8.2.6 release are 1.127 and 1.10.2.2, respectively, whereas the patch is against the head revisions.) Would it be possible to provide a patch against the 8.2.6 stable release (the one that can be downloaded from the download section of the homepage)? It seems as if partitioning is unusable without this patch because when constraint exclusion is enabled, records cannot be found by select or update even in tables where partitioning is not realized at all. On the other hand, without constraint exclusion, partitioning at all doesn't make sense (as far as I understand). Thanks a lot for your help! Regards, Christian -- Deriva GmbH Tel.: +49 551 489500-42 Financial IT and Consulting Fax: +49 551 489500-91 Hans-Böckler-Straße 2 http://www.deriva.de D-37079 Göttingen Deriva CA Certificate: http://www.deriva.de/deriva-ca.cer