Re: plpgsql.extra_warnings='num_into_expressions' - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: plpgsql.extra_warnings='num_into_expressions'
Date
Msg-id CAFj8pRDbmF-bwuJ5ZMz4DLn-zmF=_VUBHAXr2vkKe3Mz0456HA@mail.gmail.com
Whole thread Raw
In response to plpgsql.extra_warnings='num_into_expressions'  (Marko Tiikkaja <marko@joh.to>)
Responses Re: plpgsql.extra_warnings='num_into_expressions'  (Marko Tiikkaja <marko@joh.to>)
List pgsql-hackers
Hi

I looked on this patch and I am thinking so it is not a good idea. It introduce  early dependency between functions and pg_class based objects.

This check should not be integrated to function validation directly.

We can integrate it to plpgsql_check

Regards

Pavel


2014-07-21 22:56 GMT+02:00 Marko Tiikkaja <marko@joh.to>:
Hi again,

Here's a patch which allows you to notice those annoying bugs with INTO slightly more quickly.  Adding to the next commit phest.


.marko


--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers


pgsql-hackers by date:

Previous
From: Fabien COELHO
Date:
Subject: Re: small doccumentation fix in psql
Next
From: Rajmohan C
Date:
Subject: how to skip building certain paths in path tree