Skip site navigation (1) Skip section navigation (2)

BUG #1733: Function visibility in transactions error

From: "Robert Grabowski" <grabba(at)env(dot)pl>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #1733: Function visibility in transactions error
Date: 2005-06-27 15:07:00
Message-ID: 20050627150700.40D27F0B19@svr2.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-bugs
The following bug has been logged online:

Bug reference:      1733
Logged by:          Robert Grabowski
Email address:      grabba(at)env(dot)pl
PostgreSQL version: 8.0.1
Operating system:   Linux 2.6.12-gentoo
Description:        Function visibility in transactions error
Details: 

I have problem with function visibility in transaction when I do create and
drop function. There is an example.

I have two sessions:

1: CREATE FUNCTION test () RETURNS integer AS 'select 1' LANGUAGE 'sql';
CREATE FUNCTION

1: SELECT test();
 test
------
    1
(1 row)

2: BEGIN TRANSACTION ISOLATION LEVEL SERIALIZABLE;
BEGIN

2: SELECT test();
 test
------
    1
(1 row)

1: DROP FUNCTION test ();
DROP FUNCTION


1: CREATE FUNCTION test () RETURNS integer AS 'select 2' LANGUAGE 'sql';
CREATE FUNCTION

1: SELECT test();
 test
------
    2
(1 row)

2: SELECT test();
 test
------
    1
(1 row)

It's ok. In transaction I have old definition of test function.

2: SELECT test();
 test
------
    2
(1 row)

!!!! Strange! Second call of the same function gets  other result. 

In READ COMMITED transactions I have the same results.

Responses

pgsql-bugs by date

Next:From: Bruce MomjianDate: 2005-06-28 00:44:58
Subject: Re: [BUGS] BUG #1707: statistics collector starts with stats_start_collector
Previous:From: Stephan SzaboDate: 2005-06-27 14:52:45
Subject: Re: Relational operators

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group