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: Tue, 17 Jul 2007 07:59:32 +0200
Message-ID: <469C5AC4.7040903@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>

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






view thread (14+ messages)  latest in thread

Message-ID: <469C5AC4.7040903@eurofer.be>
Permalink:  ../469C5AC4.7040903@eurofer.be/
Also on:    postgresql.org/message-id/469C5AC4.7040903@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: <469C5AC4.7040903@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