| From: | "Tom Dunstan" <pgsql(at)tomd(dot)cc> |
|---|---|
| To: | "Martijn van Oosterhout" <kleptog(at)svana(dot)org> |
| Cc: | "Aidan Van Dyk" <aidan(at)highrise(dot)ca>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Gregory Stark" <stark(at)enterprisedb(dot)com>, "Jeremy Drake" <pgsql(at)jdrake(dot)com>, "Peter Eisentraut" <peter_e(at)gmx(dot)net>, "PostgreSQL Hackers" <pgsql-hackers(at)postgresql(dot)org>, "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "Greg Sabino Mullane" <greg(at)turnstep(dot)com> |
| Subject: | Re: modules |
| Date: | 2008-04-05 12:07:27 |
| Message-ID: | ca33c0a30804050507t5e2b6498pa1eb8aeb90c41d71@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Sat, Apr 5, 2008 at 5:11 PM, Martijn van Oosterhout
<kleptog(at)svana(dot)org> wrote:
> It even went so far that you could build the install/deinstall scripts
> into the module itself, so all postgres had to do was dlopen() the
> module it could access the install script. It fails due to the fact
> that modules that don't require compilation are left out in the cold...
Well, there's no reason you can't allow both... look for
module_install() in the lib if it's there, or install.sql if it's not.
Cheers
Tom
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Allison | 2008-04-05 12:15:16 | mac ports question |
| Previous Message | Volkan YAZICI | 2008-04-05 11:47:25 | Re: default value based on select |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2008-04-05 12:38:39 | Re: [HACKERS] Patch queue -> wiki |
| Previous Message | Martijn van Oosterhout | 2008-04-05 11:41:20 | Re: modules |