Re: proposal: new contrib module plpgsql's embeded sql validator

From: Petr Jelínek <pjmodos(at)pjmodos(dot)net>
To: Jim Nasby <jim(at)nasby(dot)net>
Cc: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: proposal: new contrib module plpgsql's embeded sql validator
Date: 2011-07-19 19:15:46
Message-ID: 4E25D7E2.6090805@pjmodos.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 07/17/2011 10:31 PM, Jim Nasby wrote:
> On Jul 7, 2011, at 11:31 PM, Pavel Stehule wrote:
>> a lazy deep SQL validation inside plpgsq functions is interesting
>> attribute. It allows to work with temporary tables and it make testing
>> and debugging harder, because lot of errors in embedded queries are
>> detected too late. I wrote a simple module that can to help little
>> bit. It is based on plpgsql plugin API and it ensures a deep
>> validation of embedded sql early - after start of execution. I am
>> thinking, so this plugin is really useful and it is example of plpgsql
>> pluging - that is missing in contrib.
> I think this should at least be a contrib module; it seems very useful.
>

Yes I agree this should be part of pg distribution.

But, I think we should add valitation hook to plpgsql plugin structure
so that you don't have to actually execute the function to check it -
curretly there are only executing hooks which is why the plugin only
works when you the func (not good for automation).

--
Petr Jelinek

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Gurjeet Singh 2011-07-19 19:17:19 A few user-level questions on Streaming Replication and pg_upgrade
Previous Message Andrew Dunstan 2011-07-19 19:10:25 Re: pg_upgrade and log file output on Windows