From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: module archive |
Date: | 2007-10-26 09:48:23 |
Message-ID: | 20071026094823.GA24394@svana.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Oct 25, 2007 at 12:31:30PM -0400, Andrew Dunstan wrote:
>
> From time to time people have raised the idea of a CPAN-like mechanism
> for downloading, building and installing extensions and the like (types,
> functions, sample dbs, anything not requiring Postgres itself to be
> rebuilt), and I have been thinking on this for the last few days. What
> sort of requirements would people have of such a mechanism? How do
> people envision it working?
There's been some discussion before:
http://archives.postgresql.org/pgsql-patches/2006-05/msg00327.php
The most useful feature IMHO would be if the installed modules could be
recognised as a block (using pg_depends) so that:
1. pg_dump can see them and emit only INSTALL <module>
2. Uninstall removes everything that was installed
This only covers installtion though, not building or compiling.
Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.
From | Date | Subject | |
---|---|---|---|
Next Message | Gokulakannan Somasundaram | 2007-10-26 09:48:50 | Re: [HACKERS] Including Snapshot Info with Indexes |
Previous Message | Heikki Linnakangas | 2007-10-26 09:32:09 | Re: Autovacuum cancellation |