| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
| Cc: | Islam Hegazy <islheg(at)hotmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: modifying the tbale function |
| Date: | 2007-03-18 21:26:31 |
| Message-ID: | 45FDAE87.2090503@dunslane.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Martijn van Oosterhout wrote:
> What you want is that when you call a perl tablefunction that as soon
> as the perl function returns a row to return that to the caller. That
> means the perl interpreter has to be able to save all its state,
> return to the caller and when next called resume where it left off.
> I don't know if it can do that, but it would have to be implemented for
> each language (or use threads).
>
>
>
We haven't even worked out how to do that cleanly for plpgsql, which we
control, let alone for any third party interpreter.
I'm not convinced it would be a huge gain anyway. Switching madly in and
out of the perl interpreter at least is a known performance problem,
IIRC - Perl XML objects have, or used to have, problems with that (and
they still don't perform terribly well).
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Neil Conway | 2007-03-18 22:57:57 | Re: modifying the tbale function |
| Previous Message | Andrew Dunstan | 2007-03-18 21:07:37 | Re: Bug in UTF8-Validation Code? |