| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| 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:17:57 |
| Message-ID: | 12025.1257556677@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2009-11-07 01:20:34 | Re: plperl and inline functions -- first draft |
| Previous Message | Tom Lane | 2009-11-07 01:14:35 | Re: Quoting oddities when defining operators in postgres 8.3 |