> Wow, that's been broken since the beginning, apparently. There's an
> entirely bogus test in exec_stmt_getdiag():
Thanks for quick fix! :)
Best regards,
--
Adam Buraczewski
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.post
abura...@gmail.com writes:
> I have just found strange behaviour of PL/pgSQL in case of using OUT
> parameters and GET DIAGNOSTICS var = ROW_COUNT (PostgreSQL 9.1.3). Here is a
> self-contained example:
Wow, that's been broken since the beginning, apparently. There's an
entirely bogus test in exe
wrote:
> x1 | x2 | x3
> ++
> | 1 | 1
To reduce the ambiguity about what value is coming from where, I
slightly modified the script before testing it against a recent HEAD
build:
create table t (c integer);
create function p(out x1 integer, out x2 integer, out x3 integer)
The following bug has been logged on the website:
Bug reference: 6551
Logged by: Adam Buraczewski
Email address: abura...@gmail.com
PostgreSQL version: 9.1.3
Operating system: Linux (Fedora 16)
Description:
Hi!
I have just found strange behaviour of PL/pgSQL in case
