pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: De Leeuw Guy <G.De_Leeuw@eurofer.be>
To: Andrew Sullivan <ajs@crankycanuck.ca>
Cc: pgsql-admin@postgresql.org
Subject: Re: cache problem (v2)
Date: Mon, 16 Jul 2007 22:50:13 +0200
Message-ID: <469BDA05.9010701@eurofer.be> (raw)
In-Reply-To: <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>
	<20070716203641.GF18049@phlogiston.dyndns.org>


> 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.
No the complete example need also db schema and data.
I try to reproduce with a small program.
>   
>
>   
>>> 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
>
>   
I check that tomorrow (I'm tired, 22h49h in Belgium) :-)
thanks for your help
Guy



view thread (14+ messages)  latest in thread

Message-ID: <469BDA05.9010701@eurofer.be>
Permalink:  ../469BDA05.9010701@eurofer.be/
Also on:    postgresql.org/message-id/469BDA05.9010701@eurofer.be

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: G.De_Leeuw@eurofer.be, ajs@crankycanuck.ca
  Subject: Re: cache problem (v2)
  In-Reply-To: <469BDA05.9010701@eurofer.be>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox