| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Ram Pratap Maurya <ram(dot)maurya(at)lavainternational(dot)in> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Michael Paquier <michael(at)paquier(dot)xyz>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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-19 11:37:23 |
| Message-ID: | 20200619113723.GA19125@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Jun 19, 2020 at 05:20:21AM +0000, Ram Pratap Maurya wrote:
> Dear All,
>
> any impact of server. If we Can reset manually postgres old version (11) WAL segment size .
You can change the wal segment size _after_ running pg_upgrade, but for
the upgrade, they have to match. Use an initdb flag so they do.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EnterpriseDB https://enterprisedb.com
The usefulness of a cup is in its emptiness, Bruce Lee
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2020-06-19 11:58:35 | BUG #16505: ssl_crl_file bug? |
| Previous Message | Ram Pratap Maurya | 2020-06-19 11:00:53 | RE: BUG #16497: old and new pg_controldata WAL segment sizes are invalid or do not match |