| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Joshua Tolley <eggyknap(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: plperl and inline functions -- first draft |
| Date: | 2009-11-06 23:37:38 |
| Message-ID: | 4AF4B342.6030605@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I wrote:
>
> Ok, I have a handle on the trusted/nontrusted issue. But I think the
> piece that's missing here is that it needs to save the calling context
> etc. and use PG_TRY() and friends, just like plperl_call_handler().
> I'll work on that.
>
>
OK, I committed the previously discussed change to store the language
trusted flag in the InlineCodeBlock structure. Following that, here is
my reworking of Josh's patch for DO blocks for plperl.
Missing are docs and regression tests.
cheers
andrew
| Attachment | Content-Type | Size |
|---|---|---|
| plperl-inline.patch | text/x-patch | 4.9 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-11-07 00:05:13 | Re: operator exclusion constraints |
| Previous Message | Marc Munro | 2009-11-06 23:28:49 | Quoting oddities when defining operators in postgres 8.3 |