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

Re: BUG #6043: Compilation PLpgsql Succesful but execution bad

From: Emanuel Calvo <postgres(dot)arg(at)gmail(dot)com>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #6043: Compilation PLpgsql Succesful but execution bad
Date: 2011-05-28 14:23:27
Message-ID: BANLkTinqSHoCNarnwS4vTx+xjkyWeGypqQ@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-bugs
>>
>> Thanks Heikki for your fast response! ^^
>>
>>
>>> The compiler would have to determine that the loop never ends, or it
>>> would complain that there's no RETURN at the end.
>>>
>>> Many compilers for other languages do that kind of analysis, but it
>>> usually only results in a warning, and compilers sometimes get that
>>> wrong. I don't think it's worthwhile to do that, but of course, patches
>>> are welcome.
>>>
>>
>> Yeah, it's not a very big concern, althougth cold be taken for future
>> improvements
>> in plpgsql. I very far for submit a patch :P
>>
>
> The deep check of embedded SQL is not possible in PL/pgSQL -  this
> remove dependency between PL/pgSQL and database objects. Deeper checks
> mean a broken compatibility :(.
>

Good point.

> PL/PSM has different philosophy where full check is implemented now.
>

Do you think that make some test in 9.1  worthwhile for this
language? I see that the last contrib was submitted years ago.

Regards,


-- 
--
              Emanuel Calvo
              Helpame.com

In response to

Responses

pgsql-bugs by date

Next:From: Pavel StehuleDate: 2011-05-28 14:36:28
Subject: Re: BUG #6043: Compilation PLpgsql Succesful but execution bad
Previous:From: Pavel StehuleDate: 2011-05-28 11:53:50
Subject: Re: BUG #6043: Compilation PLpgsql Succesful but execution bad

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