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

From Marko Tiikkaja
Subject Re: plpgsql.extra_warnings='num_into_expressions'
Date
Msg-id 53CE0A44.5080001@joh.to
Whole thread Raw
In response to Re: plpgsql.extra_warnings='num_into_expressions'  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: plpgsql.extra_warnings='num_into_expressions'  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
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.


.marko



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: [bug fix] Suppress "autovacuum: found orphan temp table" message
Next
From: Heikki Linnakangas
Date:
Subject: Re: Index-only scans for multicolumn GIST