Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 4B5BE9FB5D1 for ; Mon, 16 Jul 2007 17:23:07 -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 21993-04 for ; Mon, 16 Jul 2007 17:22:51 -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 49B369FB43B for ; Mon, 16 Jul 2007 17:23:04 -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 482AE838077; Mon, 16 Jul 2007 22:22:53 +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 1IAX5W-0002lJ-PL; Mon, 16 Jul 2007 22:22:53 +0200 Message-ID: <469BD389.4030606@eurofer.be> Date: Mon, 16 Jul 2007 22:22:33 +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> In-Reply-To: <20070716184837.GB18049@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/163 X-Sequence-Number: 26144 > This is also opaque to me now, because that doesn't seem to be what > your example said. Perhaps you should post your function body? > Yes, but maybe the post are too big, can I send it to your address ? It's written in C > 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 ? regards Guy