X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id D58BBD1CCA2 for ; Sun, 25 Jan 2004 16:16:43 +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 89948-08 for ; Sun, 25 Jan 2004 12:16:12 -0400 (AST) Received: from anchor-post-32.mail.demon.net (anchor-post-32.mail.demon.net [194.217.242.90]) by svr1.postgresql.org (Postfix) with ESMTP id F3C89D1D1A4 for ; Sun, 25 Jan 2004 12:16:09 -0400 (AST) Received: from lfix.demon.co.uk ([80.177.205.209] helo=cerberus.lfix.co.uk) by anchor-post-32.mail.demon.net with esmtp (Exim 3.35 #1) id 1Akmvg-000JYi-0W; Sun, 25 Jan 2004 16:16:08 +0000 Received: from linda.lfix.co.uk ([192.168.1.1]) by cerberus.lfix.co.uk with esmtp (Exim 4.30) id 1Akmvc-0006dJ-Tr; Sun, 25 Jan 2004 16:16:04 +0000 Subject: Re: Selects query inside function must read commited data From: Oliver Elphick To: aspire420@hotpop.com Cc: pgsql-admin@postgresql.org In-Reply-To: <40138377.2070503@sancharnet.in> References: <40138377.2070503@sancharnet.in> Content-Type: text/plain Organization: LFIX Limited Message-Id: <1075047334.1491.16.camel@linda.lfix.co.uk> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Sun, 25 Jan 2004 16:15:34 +0000 Content-Transfer-Encoding: 7bit X-LFIX-MailScanner: Found to be clean X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/198 X-Sequence-Number: 12061 On Sun, 2004-01-25 at 08:51, V i s h a l Kashyap @ [Sai Hertz And Control Systems] wrote: > Since sai_func_a() which encapsulates the function sai_func_b has not > completed yet till #4 or #5 > then how does the function sai_func_b reads the new data since it is > not committed yet. > > If I am not wrong PostgreSQL select statements works on committed data > thus the new > inserted data at #3 must not be available to sai_func_b() till #5 No. All operations by a single transaction are visible inside the transaction. Therefore an encapsulated function can see anything already done in the whole transaction. A function must be entirely inside a transaction and cannot start a transaction, so there can never be any problem about this. Within a transaction, you cannot see data committed by any _other_ transaction that had not already committed when your transaction started. -- Oliver Elphick Oliver.Elphick@lfix.co.uk Isle of Wight, UK http://www.lfix.co.uk/oliver GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839 932A 614D 4C34 3E1D 0C1C ======================================== "My little children, let us not love in word, neither in tongue; but in deed and in truth." I John 3:18