2012/3/5 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
>> I found a plpgsql bug:
>> create or replace function fx()
>> returns void as $$
>> declare a int; b int;
>> select 10,20 into a;
>> $$ language plpgsql;
>> this is bug, or minimally potential source of strange behave.
> AFAICS this is intentional --- see the comment in exec_move_row.
> In any case, I think tightening it up is more likely to break working
> applications than do anything helpful.
I agree with you about break working application :( But this is good
example what should be checked in CHECK statement.
but it should be bug - it has no sense - no in this form - it is
assign row to scalar.
I found a some mysterious and very difficult identified bugs in one
application based on this behave.
> regards, tom lane
In response to
pgsql-bugs by date
|Next:||From: Euler Taveira de Oliveira||Date: 2012-03-05 22:40:53|
|Subject: Re: BUG #6519: Server doesn't listem|
|Previous:||From: Tom Lane||Date: 2012-03-05 19:36:17|
|Subject: Re: plpgsql doesn't check a number of expressions and number of target variables correctly |