| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "David E(dot) Wheeler" <david(at)kineticode(dot)com>, Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: First feature patch for plperl - draft [PATCH] |
| Date: | 2009-12-05 18:28:04 |
| Message-ID: | 20091205182804.GB9381@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane escribió:
> "David E. Wheeler" <david(at)kineticode(dot)com> writes:
> > Tom, what's your objection to Shlib load time being user-visible?
>
> It's not really designed to be user-visible. Let me give you just
> two examples:
>
> * We call a plperl function for the first time in a session, causing
> plperl.so to be loaded. Later the transaction fails and is rolled
> back.
I don't think there's any way for this to work sanely unless the library
has been loaded previously. What about allowing those settings only if
plperl is specified in shared_preload_libraries?
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2009-12-05 18:56:03 | Re: New VACUUM FULL |
| Previous Message | Heikki Linnakangas | 2009-12-05 18:19:25 | Re: Summary and Plan for Hot Standby |