čt 28. 2. 2019 v 19:20 odesílatel Tom Lane <tgl@sss.pgh.pa.us> napsal:
Pavel Stehule <pavel.stehule@gmail.com> writes: > Maybe we should to disallow variables named as sql reserved keyword.
That would just break existing code. There are lots of other examples where you can get away with such things.
We've expended quite a lot of sweat to avoid reserving more names than we had to in plpgsql. I'm disinclined to throw that away just because somebody found an error message confusing. It's not like reserving "offset" would cause this case to work.
partially I solved it with new warning in plpgsql_check