Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id B9D979FBADF for ; Tue, 17 Jul 2007 02:59:54 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 35939-08-2 for ; Tue, 17 Jul 2007 02:59:49 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from BRUBLUmx12.mactelecom.net (BRUBLUmx12.mactelecom.net [217.64.240.4]) by postgresql.org (Postfix) with ESMTP id 51B249FB3D8 for ; Tue, 17 Jul 2007 02:59:51 -0300 (ADT) Received: from smtp.eurofer.be (217.64.254.218.mactelecom.net [217.64.254.218]) by BRUBLUmx12.mactelecom.net (Postfix) with ESMTP id 248038380A2; Tue, 17 Jul 2007 07:59:50 +0200 (CEST) Received: from ip-80-236-225-235.dsl.scarlet.be ([80.236.225.235] helo=[192.168.1.105]) by smtp.eurofer.be with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from ) id 1IAg5t-00052w-K7; Tue, 17 Jul 2007 07:59:49 +0200 Message-ID: <469C5AC4.7040903@eurofer.be> Date: Tue, 17 Jul 2007 07:59:32 +0200 From: De Leeuw Guy User-Agent: IceDove 1.5.0.10 (X11/20070329) MIME-Version: 1.0 To: Andrew Sullivan CC: pgsql-admin@postgresql.org References: <469B4927.9030604@eurofer.be> <20070716170957.GV18049@phlogiston.dyndns.org> <469BAF1D.8030108@eurofer.be> <20070716184837.GB18049@phlogiston.dyndns.org> <469BD389.4030606@eurofer.be> <20070716203641.GF18049@phlogiston.dyndns.org> In-Reply-To: <20070716203641.GF18049@phlogiston.dyndns.org> X-Enigmail-Version: 0.94.2.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam_score: -3.9 X-SA-Exim-Connect-IP: 80.236.225.235 X-SA-Exim-Mail-From: G.De_Leeuw@eurofer.be Subject: Re: cache problem (v2) X-SA-Exim-Scanned: Yes (on smtp.eurofer.be) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200707/169 X-Sequence-Number: 26150 Hello Andrew > You can see things that happened in your own transaction, but nobody > else can. If you're working READ COMMITTED, you can also see work > that other transactions commit while you were working. Could any of > that be affecting you? Unless your own function is doing something > with some cache, I am positive there's no cache issue here as you > describe it. > > I read the documentation : http://www.postgresql.org/docs/8.2/interactive/transaction-iso.html#XACT-SERIALIZABLE and it's maybe my problem the COPY start a transaction ? if yes each time my trigger select a data and update then the value returned by the read are the value before the transaction. It's true ? if yes my question are : also in the same transaction (like my trigger) ? Great thanks Guy