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 CAFj8pRAZsBAD4dSKH0ZrMf20JmGcKdc47UcykAmhYdR0fjeVRQ@mail.gmail.com
Whole thread Raw
In response to Re: plpgsql.extra_warnings='num_into_expressions'  (Marko Tiikkaja <marko@joh.to>)
List pgsql-hackers



2014-07-22 8:52 GMT+02:00 Marko Tiikkaja <marko@joh.to>:
On 7/22/14, 7:06 AM, Pavel Stehule wrote:
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.

What dependency?  The patch only looks at the raw parser output, so it won't e.g. know whether  SELECT * INTO a, b FROM foo;  is problematic or not.

I am sorry, I was confused

There is dependencty in variable type, but this dependency is not new.

Regards

Pavel


 


.marko

pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Index-only scans for multicolumn GIST
Next
From: Michael Paquier
Date:
Subject: Re: Production block comparison facility