On Sat, Jan 4, 2014 at 1:00 PM, Tom Lane <t...@sss.pgh.pa.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? 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. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
