Re: review: CHECK FUNCTION statement - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: review: CHECK FUNCTION statement
Date
Msg-id 1330754388-sup-5287@alvh.no-ip.org
Whole thread Raw
In response to Re: review: CHECK FUNCTION statement  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: review: CHECK FUNCTION statement  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
Excerpts from Pavel Stehule's message of sáb mar 03 02:45:06 -0300 2012:

> > Without correct registration you cannot to call PL check function
> > directly simply. I don't thing so this is good price for removing a
> > few SPI lines. I don't understand why you don't like SPI.

I don't dislike SPI in general.  I just dislike using it internally in
the backend.  Other than RI, it's not used anywhere.

> > It is used more times in code for similar purpose.
>
> this disallow direct PL check function call - so any more complex
> situation cannot be solved by SQL, but must be solved by PL/pgSQL with
> dynamic SQL

Nonsense.  Where did you get this idea?  I did not touch the plpgsql
code at all, it'd still work exactly as in your original patch.

--
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support


pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: review: CHECK FUNCTION statement
Next
From: Pavel Stehule
Date:
Subject: Re: review: CHECK FUNCTION statement