Re: Relax requirement for INTO with SELECT in pl/pgsql
От | Jim Nasby |
---|---|
Тема | Re: Relax requirement for INTO with SELECT in pl/pgsql |
Дата | |
Msg-id | 56F2BD06.7020808@BlueTreble.com обсуждение исходный текст |
Ответ на | Re: Relax requirement for INTO with SELECT in pl/pgsql (Merlin Moncure <mmoncure@gmail.com>) |
Ответы |
Re: Relax requirement for INTO with SELECT in pl/pgsql
|
Список | pgsql-hackers |
On 3/22/16 8:37 AM, Merlin Moncure wrote: >> I afraid of useless and forgotten call of functions. But the risk is same >> >like PERFORM - so this is valid from one half. The PERFORM statement holds >> >special semantic, and it is interesting. > I see your point here, but the cost of doing that far outweighs the > risks. And I don't think the arbitrary standard of defining forcing > the user to identify if the query should return data is a good way of > identifying dead code. Not to mention that there's tons of other ways to introduce unintended inefficiencies. Off the top of my head, declaring variables that are never referenced and have no assignment is a big one. -- Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX Experts in Analytics, Data Architecture and PostgreSQL Data in Trouble? Get it in Treble! http://BlueTreble.com
В списке pgsql-hackers по дате отправления: