Re: BUG #5043: Stored procedure returning different results for same arguments

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Martin Edlman" <edlman(at)fortech(dot)cz>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5043: Stored procedure returning different results for same arguments
Date: 2009-09-08 14:21:50
Message-ID: 25811.1252419710@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"Martin Edlman" <edlman(at)fortech(dot)cz> writes:
> When I call "select get_schemebind_date(1004,'2009-09-01')" from psql I get
> correct result, which is 2009-09-01.
> But when I call it from within another sp (let's call it xfunc(int, date,
> varchar), I get wrong result 2008-11-01.

The only thought that comes to mind is that maybe you've got two
tables named schemebind in different schemas, and the other function
is changing the search_path?

However, 8.2.0 is exceedingly out of date and full of known bugs.
Really the first thing you ought to do is update to 8.2.latest.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Dennis C. Seran 2009-09-08 14:37:27 Re: BUG #5036: Advisory locks have unexpected behavior
Previous Message Pavel Stehule 2009-09-08 13:40:52 Re: BUG #5043: Stored procedure returning different results for same arguments