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

Re: BUG #1733: Function visibility in transactions error

From: Robert Grabowski <grabba(at)env(dot)pl>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #1733: Function visibility in transactions error
Date: 2005-06-28 06:49:40
Message-ID: 42C0F304.6070008@env.pl (view raw or flat)
Thread:
Lists: pgsql-bugs
Tom Lane wrote:
> "Robert Grabowski" <grabba(at)env(dot)pl> writes:
> 
>>I have problem with function visibility in transaction when I do create and
>>drop function.
> 
> 
> System catalog lookups generally follow SnapshotNow rules, not MVCC.
> So the new function definition is visible as soon as it's committed,
> whether you are in a serializable transaction or not.
> 
> 			regards, tom lane
> 
> 

Hi!

OK. I can understand that. But why at first call after update function 
have I results of the old function, and at second call in the same 
transaction I have results of the new function. It is strange for me.

pozdrawiam
    Robert Grabowski





In response to

pgsql-bugs by date

Next:From: Neil ConwayDate: 2005-06-28 08:32:46
Subject: Re: BUG #1733: Function visibility in transactions error
Previous:From: Tom LaneDate: 2005-06-28 06:16:31
Subject: Re: BUG #1733: Function visibility in transactions error

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