Re: Extensions User Design

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