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

From Pavel Stehule
Subject Re: review: CHECK FUNCTION statement
Date
Msg-id CAFj8pRAm5W=0X6ApD6_QDceHwS9A46MJtz6ey6tGmdeQWUjbUg@mail.gmail.com
Whole thread Raw
In response to Re: review: CHECK FUNCTION statement  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
2012/3/3 Alvaro Herrera <alvherre@commandprompt.com>:
>
> 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.


ok

I am sorry

Pavel

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


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: review: CHECK FUNCTION statement
Next
From: Simon Riggs
Date:
Subject: Re: RFC: Making TRUNCATE more "MVCC-safe"