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

From Alvaro Herrera
Subject Re: review: CHECK FUNCTION statement
Date
Msg-id 1322591849-sup-4633@alvh.no-ip.org
Whole thread Raw
In response to Re: review: CHECK FUNCTION statement  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
Excerpts from Pavel Stehule's message of mar nov 29 14:37:24 -0300 2011:
> 2011/11/29 Tom Lane <tgl@sss.pgh.pa.us>:

> > I don't think renaming is necessary.  plpgsql is a standalone shared
> > library and so its symbols don't matter to anybody but itself.
> >
> > Possibly a larger question, though, is whether you really need a new
> > source file.  If that results in having to export functions that
> > otherwise could stay static, maybe it's not the best choice.
>

> Some refactoring of pl_exec should be nice - a management of row,
> record variables and array fields is part that can be shared with
> SQL/PSM interpret. But I have not idea how it realize.

I proposed at the PL summit that perhaps we should have some sort of PL
lib that would be shared by plpgsql and plpsm, to reduce code
duplication.

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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [Review] Include detailed information about a row failing a CHECK constraint into the error message
Next
From: Jan Kundrát
Date:
Subject: Re: [Review] Include detailed information about a row failing a CHECK constraint into the error message