Re: creating and accessing temp table data inside a non-committed transaction

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Leon Starr" <leon_starr(at)modelint(dot)com>, <pgsql-admin(at)postgresql(dot)org>
Subject: Re: creating and accessing temp table data inside a non-committed transaction
Date: 2011-01-31 15:42:04
Message-ID: 4D4683EC020000250003A01A@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Leon Starr <leon_starr(at)modelint(dot)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

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Leon Starr 2011-01-31 17:11:11 Re: creating and accessing temp table data inside a non-committed transaction
Previous Message McKee, Shawn 2011-01-31 14:00:14 Unable to setup hot-standy for Postgresql 9.0.2 "seeded"