| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, Fabrizio Mello <fabriziomello(at)gmail(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] Store Extension Options |
| Date: | 2014-01-06 03:39:50 |
| Message-ID: | 7585.1388979590@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Sun, Jan 5, 2014 at 3:45 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> pg_dump creates extensions before tables, no? So what dump/restore
>> hazard?
> Creating the extension doesn't guarantee that the shared library will
> always be loaded.
No, but unless the plan is that no validation happens at all (which
I gather is not your desire) then there must be some mechanism for
figuring out which extension owns a given reloption and asking it
to validate the value. This might be more complicated than a passive
hook, but I don't feel bad about demanding that it work like that.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-01-06 03:50:53 | Re: [PATCH] Store Extension Options |
| Previous Message | Craig Ringer | 2014-01-06 03:32:02 | Compiling extensions on Windows |