Re: plpgsql.extra_warnings='num_into_expressions'

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

2014-07-22 8:52 GMT+02:00 Marko Tiikkaja <marko(at)joh(dot)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
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2014-07-22 07:49:12 Re: Production block comparison facility
Previous Message Heikki Linnakangas 2014-07-22 06:55:07 Re: Index-only scans for multicolumn GIST