Skip site navigation (1) Skip section navigation (2)

Re: cache problem (v2)

From: De Leeuw Guy <G(dot)De_Leeuw(at)eurofer(dot)be>
To: Andrew Sullivan <ajs(at)crankycanuck(dot)ca>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: cache problem (v2)
Date: 2007-07-16 20:50:13
Message-ID: 469BDA05.9010701@eurofer.be (view raw or flat)
Thread:
Lists: pgsql-admin
> 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

In response to

pgsql-admin by date

Next:From: Vishal AroraDate: 2007-07-17 04:13:52
Subject: Re: PgAgent Job Scheduling-Backup
Previous:From: Andrew SullivanDate: 2007-07-16 20:36:41
Subject: Re: cache problem (v2)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group