X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org
Received: from localhost (unknown [200.46.204.2])
	by svr1.postgresql.org (Postfix) with ESMTP
	id 1E3E3D1B500; Fri, 31 Oct 2003 07:44:15 +0000 (GMT)
Received: from svr1.postgresql.org ([200.46.204.71])
	by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024)
	with ESMTP id 42220-06; Fri, 31 Oct 2003 03:43:44 -0400 (AST)
Received: from woodfire (ip-a1-37118.keycomm.it [62.152.37.118])
	by svr1.postgresql.org (Postfix) with ESMTP
	id 461A6D1B4F9; Fri, 31 Oct 2003 03:43:38 -0400 (AST)
Received: from localhost (localhost [127.0.0.1])
	by woodfire (Postfix) with ESMTP
	id EA733D47; Fri, 31 Oct 2003 09:44:26 +0100 (CET)
Received: from woodfire ([127.0.0.1])
	by localhost (woodfire [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 01445-03; Fri, 31 Oct 2003 09:44:20 +0100 (CET)
Received: from osts (unknown [192.168.100.27]) by woodfire (Postfix) with
 ESMTP
	id 6B9D3B56; Fri, 31 Oct 2003 09:44:20 +0100 (CET)
Subject: Re: 7.4 and 7.3.5 showstopper (was: Re: Bug in Rule+Foreing
From: Michele Bendazzoli <mickymouse@mickymouse.it>
To: Jan Wieck <JanWieck@Yahoo.com>
Cc: pgsql-sql <pgsql-sql@postgresql.org>,
	PostgreSQL-development <pgsql-hackers@postgresql.org>
In-Reply-To: <3FA162BD.8060409@Yahoo.com>
References: <1067517334.2371.26.camel@mickymouse.sintel>
	<3FA14A86.8080802@Yahoo.com>
	<1067540494.2420.45.camel@mickymouse.sintel>
	<3FA162BD.8060409@Yahoo.com>
Content-Type: text/plain
Organization: Micky Mouse
Message-Id: <1067590182.969.32.camel@mickymouse.sintel>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.5 
Date: Fri, 31 Oct 2003 09:49:42 +0100
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new-20030616-p5 (Debian) at sintelnet.it
X-Virus-Scanned: by amavisd-new at postgresql.org
X-Archive-Number: 200310/410
X-Sequence-Number: 15810

On Thu, 2003-10-30 at 20:13, Jan Wieck wrote:
> Thanks for reporting, Michele. 

Thank to you! The speed and level of your responses exceeds every my
more rose-colored expectation ;-)

> In the meantime, you might want to use a 
> BEFORE INSERT trigger in PL/pgSQL that tries to UPDATE the row and if 
> GET DIAGNOSTICS tells it it succeeded, returns NULL to suppress the 
> INSERT. That should work around the bug for the time being.

It is not a problem for me, the db is not still in production, so I
think i wait for the patch.

Thank to all you again.

ciao, Michele