Re: [GENERAL] pg_upgrade ?deficiency
От | Tom Lane |
---|---|
Тема | Re: [GENERAL] pg_upgrade ?deficiency |
Дата | |
Msg-id | 884.1385855282@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: [GENERAL] pg_upgrade ?deficiency (Kevin Grittner <kgrittn@ymail.com>) |
Ответы |
Re: [GENERAL] pg_upgrade ?deficiency
|
Список | pgsql-hackers |
Kevin Grittner <kgrittn@ymail.com> writes: > Tom Lane <tgl@sss.pgh.pa.us> wrote: >> What is the point of this, given that Kevin fixed pg_dumpall? >> Don't those fixes take care of the issue? > If there were databases or users with default_transaction_read_only > set in the old cluster, the pg_dumpall run will cause that property > to be set in the new cluster, so what you are saying seems to be > that a cluster can't be upgraded to a new major release if any > database within it has that set. Oh, I had forgotten that pg_upgrade will run additional commands against the new cluster after restoring the dumpall output. I guess we do need something like what Bruce did to cover that. regards, tom lane
В списке pgsql-hackers по дате отправления: