| From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | ram(dot)maurya(at)lavainternational(dot)in, pgsql-bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #16497: old and new pg_controldata WAL segment sizes are invalid or do not match |
| Date: | 2020-06-18 14:18:21 |
| Message-ID: | CAMkU=1zRirCC-kZTZb0hBq+jqy7vjk8+ehbrZpjr5LATKFChKQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thu, Jun 18, 2020 at 4:05 AM Michael Paquier <michael(at)paquier(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2020-06-18 14:30:03 | Re: BUG #16497: old and new pg_controldata WAL segment sizes are invalid or do not match |
| Previous Message | Ram Pratap Maurya | 2020-06-18 13:32:37 | RE: BUG #16497: old and new pg_controldata WAL segment sizes are invalid or do not match |