Re: plpgsql.extra_warnings='num_into_expressions'

From: Marko Tiikkaja <marko(at)joh(dot)to>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: plpgsql.extra_warnings='num_into_expressions'
Date: 2014-07-22 06:52:52
Message-ID: 53CE0A44.5080001@joh.to
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2014-07-22 06:55:07 Re: Index-only scans for multicolumn GIST
Previous Message Andres Freund 2014-07-22 06:31:13 Re: [bug fix] Suppress "autovacuum: found orphan temp table" message