| From: | Kineticode Billing <david(at)kineticode(dot)com> |
|---|---|
| To: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Review: Extensions Patch |
| Date: | 2010-12-08 20:21:31 |
| Message-ID: | 1394159A-9434-45DA-A32B-71EE6DBD625B@kineticode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Dec 8, 2010, at 12:18 PM, Dimitri Fontaine wrote:
>> It's certainly true that a large fraction of contrib modules should be
>> relocatable in that sense, because they just contain C functions that
>> aren't going to care.
>
> As they all currently are using the SET search_path TO public; trick, I
> think they are all relocatable as is and all I need is to remove that
> line (and add the property to the control file).
+1 This alone would be a huge improvement, solving my complaint about @extschema@ for the vast majority of cases. It's reasonable to make the author of a multi-schema extension or an extension that cannot be moved do more work.
Best,
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Urbański | 2010-12-08 20:32:58 | Re: Solving sudoku using SQL |
| Previous Message | Tom Lane | 2010-12-08 20:20:01 | Re: serializable read only deferrable |