Re: Query regarding selectDumpableExtension()
| От | Robert Haas |
|---|---|
| Тема | Re: Query regarding selectDumpableExtension() |
| Дата | |
| Msg-id | CA+Tgmob4r5XNLz-1Z1cMq4288v0MYk9yper_Pq_iWpbZ=10u2w@mail.gmail.com обсуждение исходный текст |
| Ответ на | Query regarding selectDumpableExtension() (amul sul <sulamul@gmail.com>) |
| Ответы |
Re: Query regarding selectDumpableExtension()
|
| Список | pgsql-hackers |
On Thu, Oct 27, 2016 at 2:11 AM, amul sul <sulamul@gmail.com> wrote:
> selectDumpableExtension() function skip
> s dump of
> built-in extensions in case of binary-upgrade only,
> why not in normal
> dump
> ?
> Can't we assume those will already be installed in the target database
> at restore
> ?
There's a comment in dumpExtension() that explains it.
/* * In a regular dump, we use IF NOT EXISTS so that there isn't a * problem if the extension
alreadyexists in the target database; * this is essential for installed-by-default extensions such as *
plpgsql. * * In binary-upgrade mode, that doesn't work well, so instead we skip * built-in
extensionsbased on their OIDs; see * selectDumpableExtension. */
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: