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 05:06:12
Message-ID: CAFj8pRDbmF-bwuJ5ZMz4DLn-zmF=_VUBHAXr2vkKe3Mz0456HA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)joh(dot)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(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Rajmohan C 2014-07-22 05:23:39 how to skip building certain paths in path tree
Previous Message Fabien COELHO 2014-07-22 04:58:57 Re: small doccumentation fix in psql