Received: from localhost (postgresql.org [64.49.215.8])
	by postgresql.org (Postfix) with ESMTP id C09A547648A
	for <pgsql-sql@postgresql.org>; Fri, 18 Oct 2002 03:18:49 -0400 (EDT)
Received: from smtp.umr.edu (mrelay1.cc.umr.edu [131.151.1.120])
	by postgresql.org (Postfix) with ESMTP id DC2BF476407
	for <pgsql-sql@postgresql.org>; Fri, 18 Oct 2002 03:18:48 -0400 (EDT)
Received: from umr.edu (d-131-151-186-104.dynamic.umr.edu [131.151.186.104])
	via ESMTP by mrelay1.cc.umr.edu (8.12.1/) id g9I7InGs016376;
	Fri, 18 Oct 2002 02:18:49 -0500
Message-ID: <3DAFB616.8010202@umr.edu>
Date: Fri, 18 Oct 2002 07:19:50 +0000
From: Brian Blaha <bblaha@umr.edu>
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.0.1) Gecko/20020815
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: pgsql-sql@postgresql.org
Subject: UPDATE: Apparent referential integrity bug in PL/pgSQL
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by AMaViS new-20020517
X-Archive-Number: 200210/204
X-Sequence-Number: 9921

The workaround I mentioned in the previous message doesn't turn out to 
work after all.
The series of statements seems to require explicitly calling two functions.