| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Joshua Tolley <eggyknap(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: plperl and inline functions -- first draft |
| Date: | 2009-11-07 01:20:34 |
| Message-ID: | 4AF4CB62.3020508@dunslane.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>
>> ! * plperl_call_handler and plperl_inline_handler are the only
>> ! * externally-visible parts of the plperl call interface. The Postgres function
>> ! * and trigger managers call plperl_call_handler to execute a perl function, and
>> ! * call plperl_inline_handler to execute plperl code in a DO statement.
>>
>
> This comment should be updated to mention the validator. (What it
> replaces was wrong before, but that's no excuse for not making it
> right while you're touching it.)
>
> The spacing seems a bit random too. pgindent will fix some of that,
> but it's not very bright about making vertical spacing (ie extra
> blank lines) consistent.
>
>
>
OK, I'll clean it up.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2009-11-07 01:46:24 | Re: operator exclusion constraints |
| Previous Message | Tom Lane | 2009-11-07 01:17:57 | Re: plperl and inline functions -- first draft |