From: SZŰCS Gábor <surrano@mailbox.hu>
To: pgsql-sql@postgresql.org
Subject: Delayed result from another connection
Date: Thu, 4 Nov 2004 18:19:13 +0100
Message-ID: <012601c4c292$6804b810$0403a8c0@fejleszt4> (raw)
Dear Gurus,
I have a strange scenario that doesn't seem to work flawlessly. I think I
can produce a full working example if needed.
We use postgresql 7.4.5
It's something like this:
%----------------------- cut here -----------------------%
CREATE TABLE php_retval(id serial PRIMARY KEY, retval varchar);
CREATE FUNCTION php_run(int, varchar) RETURNS varchar AS '
declare
seq ALIAS FOR $1;
php ALIAS FOR $2;
ret varchar;
begin
perform php_run_c(php, seq);
ret := retval from php_retval where id = seq;
return ret;
end;'
LANGUAGE 'plpgsql' VOLATILE STRICT;
%----------------------- cut here -----------------------%
Now, this calls a c (SPI) function that calls system() to execute "php -q"
The php connects to the database and updates retval where id=seq.
It seems to be OK, but the function returns the value of php_retval.retval
_before_ the call. However, the php does the update. If I repeat the
function call in the transaction, the new result is returned:
%----------------------- cut here -----------------------%
UPDATE php_retval SET retval='nothing' WHERE id=1;
BEGIN;
SELECT php_run(1, 'test.php');
--> 'nothing'
SELECT php_run(1, 'test.php');
--> '3', the right value
END;
%----------------------- cut here -----------------------%
I thought it's something about "35.2 Visibility of Data Changes", but that's
only for triggers, isn't it? Also, the rule "query sees results of any
previously started queries" seems to be invaded: the perform runs right
before the query for retval.
Any ideas, explanations, clarifications, points to earlier discussions, rtfm
etc?
TIA,
G.
%----------------------- cut here -----------------------%
\end
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-sql@postgresql.org
Cc: surrano@mailbox.hu
Subject: Re: Delayed result from another connection
In-Reply-To: <012601c4c292$6804b810$0403a8c0@fejleszt4>
* 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