Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id EC1619FB546 for ; Mon, 16 Jul 2007 17:37:09 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 32834-08 for ; Mon, 16 Jul 2007 17:36:43 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from main2.mycybernet.net (main2.mycybernet.net [209.222.63.140]) by postgresql.org (Postfix) with ESMTP id 8A8EA9FA240 for ; Mon, 16 Jul 2007 17:37:04 -0300 (ADT) Received: from 227-54-222-209.mycybernet.net ([209.222.54.227] helo=phlogiston.dydns.org) by main2.mycybernet.net with esmtp (Exim 4.62) (envelope-from ) id 1IAXJH-0008Pl-71; Mon, 16 Jul 2007 16:36:47 -0400 Received: by phlogiston.dydns.org (Postfix, from userid 1000) id C489C404E; Mon, 16 Jul 2007 16:36:41 -0400 (EDT) Date: Mon, 16 Jul 2007 16:36:41 -0400 From: Andrew Sullivan To: De Leeuw Guy Cc: Andrew Sullivan , pgsql-admin@postgresql.org Subject: Re: cache problem (v2) Message-ID: <20070716203641.GF18049@phlogiston.dyndns.org> References: <469B4927.9030604@eurofer.be> <20070716170957.GV18049@phlogiston.dyndns.org> <469BAF1D.8030108@eurofer.be> <20070716184837.GB18049@phlogiston.dyndns.org> <469BD389.4030606@eurofer.be> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <469BD389.4030606@eurofer.be> User-Agent: Mutt/1.5.9i X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200707/162 X-Sequence-Number: 26143 On Mon, Jul 16, 2007 at 10:22:33PM +0200, De Leeuw Guy wrote: > > > Yes, but maybe the post are too big, can I send it to your address ? > It's written in C Well, sending it to me will do you zero good, as my C skills are awful. Assuming it's a reasonable size, I think the list will take it. > > There is nothing in the cache that isn't "in the database", as it > > were, but there are visibility rules that might be affecting you. > > > visibility rules ? 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. A -- Andrew Sullivan | ajs@crankycanuck.ca Unfortunately reformatting the Internet is a little more painful than reformatting your hard drive when it gets out of whack. --Scott Morris