Re: Enable data checksums by default
От | Christoph Berg |
---|---|
Тема | Re: Enable data checksums by default |
Дата | |
Msg-id | aEFzTrnKfH6TJYVM@msg.df7cb.de обсуждение исходный текст |
Ответ на | Re: Enable data checksums by default (Heikki Linnakangas <hlinnaka@iki.fi>) |
Ответы |
Re: Enable data checksums by default
|
Список | pgsql-hackers |
Re: Heikki Linnakangas > 1. Have pg_upgrade run initdb for you. It's always felt silly that you need > to run initdb with the new version yourself, when there's really only one > correct way to do it. Fwiw, Debian's pg_upgradecluster script would be happy if that problem would be solved. Currently, we have to do all sorts of inspection of the old cluster to figure out the locale used, data checksums, and we are likely missing some more properties that could carried over (like wal segment size etc). Some of the info isn't even available from the control file but needs a connection to the running server. The problem exists for both the pg_upgrade and dump-restore upgrade methods, so an "initdb --like /path/to/other/cluster" mode would be handy to have. Perhaps including a "initdb --like --print-command" mode. The pg_{backup,restore}cluster scripts have the same problem. It's unnecessarily complex to recreate an existing setup. Maybe it would be enough if the initdb options used to create a cluster would be stored in some file in the data dir. (Perhaps in a new line in PG_VERSION? As part of the control file?) Christoph
В списке pgsql-hackers по дате отправления: