Re: [PATCH] Store Extension Options
От | Robert Haas |
---|---|
Тема | Re: [PATCH] Store Extension Options |
Дата | |
Msg-id | CA+TgmoZLe9Muwjz-5=RqXGwqq=4tMeJP0FB4Z6RnyG6+XBHRqQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [PATCH] Store Extension Options (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: [PATCH] Store Extension Options
Re: [PATCH] Store Extension Options |
Список | pgsql-hackers |
On Sun, Jan 5, 2014 at 3:45 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Robert Haas <robertmhaas@gmail.com> writes: >> On Sat, Jan 4, 2014 at 1:00 PM, Tom Lane <tgl@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? > > 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. If nothing else, think about partial restores. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: