Re: pg_upgrade
| От | Tomasz Szypowski |
|---|---|
| Тема | Re: pg_upgrade |
| Дата | |
| Msg-id | CACmJi2JJhTeecWdrH6DBTHCDW+etvu5CwODwkS_u4sSRedCW9g@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: pg_upgrade (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: pg_upgrade
|
| Список | pgsql-bugs |
Hi Tom,
thanks for the response. After initdb tempate1 has datistemplate as true and in the pg_upgrade.c is:
/*
* template1 and postgres databases will already exist in the target
* installation, so tell pg_restore to drop and recreate them;
* otherwise we would fail to propagate their database-level
* properties.
*/
create_opts = "--clean --create";
regards
Thomas Szypowski
pon., 18 mar 2019 o 15:33 Tom Lane <tgl@sss.pgh.pa.us> napisał(a):
Tomasz Szypowski <tomasz.szypowski@gmail.com> writes:
> while using pg_upgrade I receive an error:
> pg_restore: dropping DATABASE template1
> pg_restore: [archiver (db)] Error while PROCESSING TOC:
> pg_restore: [archiver (db)] Error from TOC entry 1955; 1262 1 DATABASE
> template1 postgres
> pg_restore: [archiver (db)] could not execute query: ERROR: cannot drop a
> template database
> Command was: DROP DATABASE "template1";
Hmmm ... I could believe this would happen if you've removed the
is_template marking from template1 in the source installation.
That doesn't seem like a terribly good idea though, so I'm not
inclined to try to figure a way for pg_dump to work around it.
regards, tom lane
В списке pgsql-bugs по дате отправления: