Re: [PATCH] Store Extension Options

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Sat, Jan 4, 2014 at 1:00 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> I would suggest addressing Robert's concern about lack of error checking
>> by refusing to allow a custom reloption to be set unless the relevant
>> extension is loaded and checks it. Unlike the postgresql.conf problem,
>> I don't see any very good use-case for allowing an unchecked ALTER TABLE
>> to occur.

> How do you plan to resolve the associated dump/restore hazard?

pg_dump creates extensions before tables, no? So what dump/restore
hazard?

> AIUI,
> that's why we allow people define any old this.that GUC that they want
> without checking it - because the relevant shared library might not be
> loaded at the time of definition, but only by time of use.

No, the reason we allow GUCs to be set before the relevant library is
loaded is so that you can put a setting into postgresql.conf without
thereby having to make the extension be load-into-postmaster.

regards, tom lane