| From: | Dimitri Fontaine <dfontaine(at)hi-media(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com>, "David E(dot) Wheeler" <david(at)kineticode(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Status of plperl inter-sp calling |
| Date: | 2010-01-06 15:11:30 |
| Message-ID: | 87637fqndp.fsf@hi-media-techno.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> I think what we should do is either (1) implement a poor man's caching
> that doesn't try to cope with any of these issues, and document that
> you get what you pay for or (2) reject this idea in its entirety.
> Trying to reimplement all of our normal function call semantics in a
> caching layer does not seem very sane.
What about (3) implementing the caching layer in the core code so that
any caller benefit from it? I guess the size of the project is not the
same though.
Regards,
--
dim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2010-01-06 15:34:44 | Re: [HACKERS] tribble.postgresql.org - planned maintenance downtime |
| Previous Message | Robert Haas | 2010-01-06 15:05:52 | Re: Status of plperl inter-sp calling |