pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Leon Starr <leon_starr@modelint.com>
To: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: pgsql-admin@postgresql.org
Subject: Re: creating and accessing temp table data inside a non-committed transaction
Date: Mon, 31 Jan 2011 09:11:11 -0800
Message-ID: <361581B2-4CAE-47C6-A300-F60EE79C686E@modelint.com> (raw)
In-Reply-To: <4D4683EC020000250003A01A@gw.wicourts.gov>
References: <FC69D86A-2486-4967-84C5-1E97BDC12E80@modelint.com>
	<4D4683EC020000250003A01A@gw.wicourts.gov>

Ah!  That's what I had originally thought.  So, if what you are saying is true, 
then I just have a bug of some sort.  I am NOT using any triggers.  It's just a
simple function with deeper function calls nested about 5 levels down.

To slightly rephrase:  Any database changes (inserts/updates) made by a transaction are visible
inside that transaction.  So if I do an insert inside a transaction and then later, within the same
transaction, do a select on the inserted row, I should select the data that I inserted.  Correct?

I will do my diagnostics with that in mind.  Thanks!

- Leon


On Jan 31, 2011, at 7:42 AM, Kevin Grittner wrote:

> Leon Starr <leon_starr@modelint.com> wrote:
> 
>> The problem is that the values x, y and z are inserted into a
>> permanent table Q early in the processing of my_func.  Then,
>> several calls down in deep_func(), still inside my_func, I need to
>> access the value of x.  I tried to do a select on Q to get the
>> value, but I came up NULL! Guessing that is because the
>> transaction hasn't committed yet since I am still inside my_func. 
>> Right?
> 
> I don't think so.  Any database changes made by a transaction should
> be visible to that transaction.  When you say "several calls down in
> deep_func()", you don't mean that you are in a BEFORE trigger
> function, or a function called from a BEFORE trigger, do you?
> 
> Perhaps you could boil the issue down to a small self-contained
> example of the issue?
> 
> -Kevin





view thread (4+ messages)  latest in thread

Message-ID: <361581B2-4CAE-47C6-A300-F60EE79C686E@modelint.com>
Permalink:  ../361581B2-4CAE-47C6-A300-F60EE79C686E@modelint.com/
Also on:    postgresql.org/message-id/361581B2-4CAE-47C6-A300-F60EE79C686E@modelint.com

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: leon_starr@modelint.com, Kevin.Grittner@wicourts.gov
  Subject: Re: creating and accessing temp table data inside a non-committed transaction
  In-Reply-To: <361581B2-4CAE-47C6-A300-F60EE79C686E@modelint.com>
  References: <FC69D86A-2486-4967-84C5-1E97BDC12E80@modelint.com> <4D4683EC020000250003A01A@gw.wicourts.gov> <361581B2-4CAE-47C6-A300-F60EE79C686E@modelint.com>

* 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