Re: BUG #16497: old and new pg_controldata WAL segment sizes areinvalid or do not match
| От | Jeff Janes |
|---|---|
| Тема | Re: BUG #16497: old and new pg_controldata WAL segment sizes areinvalid or do not match |
| Дата | |
| Msg-id | CAMkU=1zRirCC-kZTZb0hBq+jqy7vjk8+ehbrZpjr5LATKFChKQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: BUG #16497: old and new pg_controldata WAL segment sizes areinvalid or do not match (Michael Paquier <michael@paquier.xyz>) |
| Ответы |
Re: BUG #16497: old and new pg_controldata WAL segment sizes areinvalid or do not match
Re: BUG #16497: old and new pg_controldata WAL segment sizes are invalid or do not match |
| Список | pgsql-bugs |
On Thu, Jun 18, 2020 at 4:05 AM Michael Paquier <michael@paquier.xyz> wrote:
On Wed, Jun 17, 2020 at 09:00:23PM +0000, PG Bug reporting form wrote:
> I am facing error during upgrade from postgresql -11 to 12.
> can you please suggest what is solution.
As the error message is telling, you need to make the WAL segment
sizes of the old and new clusters match. This can be defined at
server initialization time using initdb with a default of 16MB, so
that's not a bug from us, but something you need to take care of
within your upgrade process.
Since wal-segsize is changeable with pg_resetwal since v11, and pg_upgrade is already calling pg_resetwal, shouldn't pg_upgrade ideally just deal with this situation automatically by allowing the upgrade to also change this value, rather than forcing the user to make them match manually?
Cheers,
Jeff
В списке pgsql-bugs по дате отправления: