| Lists: | pgsql-hackers |
|---|
| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: session persistent data for plperl |
| Date: | 2004-02-09 07:13:12 |
| Message-ID: | 200402082313.12850.josh@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-hackers |
Adnrew,
> The attached tiny patch (not intended for application yet) provides a
> space for plperl functions to create and share session persistent data,
> which I should think would increase the utility of plperl.
You want to really make PL/Perl more useful? Add an SPI interface, and work
out the kinks in error-trapping via eval{}. This would be far more useful
that session variables.
Just a thought.
--
Josh Berkus
Aglio Database Solutions
San Francisco
| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: session persistent data for plperl |
| Date: | 2004-02-09 12:49:11 |
| Message-ID: | 402781C7.3040209@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-hackers |
Josh Berkus wrote:
>Adnrew,
>
Jsoh :-)
>You want to really make PL/Perl more useful? Add an SPI interface, and work
>out the kinks in error-trapping via eval{}. This would be far more useful
>that session variables.
>
>Just a thought.
>
I don't intend to stop there. I admit that the gain in value from my
patch is limited, but I think it is greater than 0, and for a 2 line
change a cheap win.
When I have bedded down some other things I am working on (e.g. logging
enhancements, dollar quoting) I intend to look further at some of the
Perl issues, both on the server side and the client side. As a longtime
and fond Perl user, I don't like seeing Perl as the poor cousin PL in
our community.
cheers
andrew