| From: | Avinash Kumar <avinash(dot)vallarapu(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Geoghegan <pg(at)bowt(dot)ie>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Postgres crashes at memcopy() after upgrade to PG 13. |
| Date: | 2021-03-16 18:20:34 |
| Message-ID: | CAN0Tujdoj1X5ikHBFcqwVFpHv5eHakCotPKSgqu9unxwmBSRvA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Tue, Mar 16, 2021 at 3:08 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Peter Geoghegan <pg(at)bowt(dot)ie> writes:
> > ... It's hard to believe that the problem is
> > squarely with _bt_swap_posting().
>
> IIUC, the problem is seen on a replica server but not the primary?
> In that case, my thoughts would run towards a bug in WAL log creation
> or replay, causing the index contents to be different/wrong on the
> replica.
>
Right, observed after the replica Server after it got promoted.
The replica is of the same Postgres minor version - 13.1 but, the OS is
Ubuntu 16 on Primary and Ubuntu 20 on Replica (that got promoted).
Replica was setup using a backup taken using pg_basebackup.
I can share any detail that would help here.
> regards, tom lane
>
--
Regards,
Avi
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2021-03-16 18:23:37 | Re: Postgres crashes at memcopy() after upgrade to PG 13. |
| Previous Message | Tom Lane | 2021-03-16 18:08:11 | Re: Postgres crashes at memcopy() after upgrade to PG 13. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-03-16 18:22:34 | Re: pg_amcheck contrib application |
| Previous Message | Tom Lane | 2021-03-16 18:08:11 | Re: Postgres crashes at memcopy() after upgrade to PG 13. |