| From: | Richard Huxton <dev(at)archonet(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Andrew Dunstan <andrew(at)dunslane(dot)net>, "David E(dot) Wheeler" <david(at)kineticode(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Dimitri Fontaine <dfontaine(at)hi-media(dot)com> |
| Subject: | Re: Extensions User Design |
| Date: | 2009-06-29 13:01:33 |
| Message-ID: | 4A48BB2D.2030202@archonet.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut wrote:
>
> Another thing we might want to consider once we have a robust extension
> mechanism is to move some things out of the backend into extensions.
> Candidates could be uuid, legacy geometry types, inet/cidr, for example.
> These extensions would still be available and probably installed by default,
> but they need not be hardcoded into the backend.
Presumably would help the prospective upgrader too. Upgrade tool can't
cope with the change to inet types? No problem, I *know* they're not in
use, since they're not loaded.
--
Richard Huxton
Archonet Ltd
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lars Kanis | 2009-06-29 13:14:27 | [PATCH] user mapping extension to pg_ident.conf |
| Previous Message | Peter Eisentraut | 2009-06-29 12:48:19 | Re: Extensions User Design |