X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 571DA3A4FBC for ; Tue, 16 Nov 2004 06:52:35 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 02324-09 for ; Tue, 16 Nov 2004 06:52:25 +0000 (GMT) Received: from megazone.bigpanda.com (megazone.bigpanda.com [64.147.171.210]) by svr1.postgresql.org (Postfix) with ESMTP id 3B0523A4FB4 for ; Tue, 16 Nov 2004 06:52:25 +0000 (GMT) Received: by megazone.bigpanda.com (Postfix, from userid 1001) id 9B72A3574F; Mon, 15 Nov 2004 22:52:22 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by megazone.bigpanda.com (Postfix) with ESMTP id 8C9F435745; Mon, 15 Nov 2004 22:52:22 -0800 (PST) Date: Mon, 15 Nov 2004 22:52:22 -0800 (PST) From: Stephan Szabo To: Thomas Berg Cc: pgsql-sql@postgresql.org Subject: Re: Cascade updates wait until the end of the transaction? In-Reply-To: Message-ID: <20041115224713.K53414@megazone.bigpanda.com> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200411/138 X-Sequence-Number: 19457 On Fri, 12 Nov 2004, Thomas Berg wrote: > Within a function (and therefore within a transaction), if I UPDATE the > primary key of a table, the old value remains visible in the child table > through the end of the function. Is this 8.0 runs immediate triggers after each statement of a function and also forces referential actions to be treated as immediate and as such should change the behavior mentioned.