pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Andrew Sullivan <ajs@crankycanuck.ca>
To: pgsql-admin@postgresql.org
Subject: Re: cache problem (v2)
Date: Tue, 17 Jul 2007 11:28:49 -0400
Message-ID: <20070717152848.GD21688@phlogiston.dyndns.org> (raw)
In-Reply-To: <469C5AC4.7040903@eurofer.be>
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>
	<469C5AC4.7040903@eurofer.be>

On Tue, Jul 17, 2007 at 07:59:32AM +0200, De Leeuw Guy wrote:
> the COPY start a transaction 

Yes.  _Everything_ is in a transaction in PostgreSQL.  If you don't
explicitly do BEGIN. . .COMMIT, then the system does it implicitly
for each statement.

> 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) ?

Your trigger function runs inside the transaction of the calling
statement, unless you have explicitly started a transaction. 

I'm starting to get the impression you have a misunderstanding of how
PostgreSQL works.  I think you maybe need to spend some more time
with the manual.  If you find the English version puzzling, you can
also work in French (at http://docs.postgresqlfr.org/) or German (I
see a translation at
http://www.postgresql.org/docs/books/pghandbuch.html.de; I dunno if
there's a more recent one).  Sorry, AFAIK there isn't one in Dutch.

A

-- 
Andrew Sullivan  | ajs@crankycanuck.ca
The whole tendency of modern prose is away from concreteness.
		--George Orwell



view thread (14+ messages)  latest in thread

Message-ID: <20070717152848.GD21688@phlogiston.dyndns.org>
Permalink:  ../20070717152848.GD21688@phlogiston.dyndns.org/
Also on:    postgresql.org/message-id/20070717152848.GD21688@phlogiston.dyndns.org

 · 

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: ajs@crankycanuck.ca
  Subject: Re: cache problem (v2)
  In-Reply-To: <20070717152848.GD21688@phlogiston.dyndns.org>

* 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