| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | Avinash Kumar <avinash(dot)vallarapu(at)gmail(dot)com> |
| Cc: | PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Postgres crashes at memcopy() after upgrade to PG 13. |
| Date: | 2021-03-15 00:39:53 |
| Message-ID: | CA+hUKGJHBMB+mMxxhR7LbhEjKUeqV5gUx5PDB-P5ti_Rx6sOvg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Mon, Mar 15, 2021 at 1:29 PM Avinash Kumar
<avinash(dot)vallarapu(at)gmail(dot)com> wrote:
> Is this expected when replication is happening between PostgreSQL databases hosted on different OS versions like Ubuntu 16 and Ubuntu 20 ? Or, do we think this is some sort of corruption ?
Is this index on a text datatype, and using a collation other than "C"?
https://wiki.postgresql.org/wiki/Locale_data_changes
Not that I expect it to crash if that's the cause, I thought it'd just
get confused.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Avinash Kumar | 2021-03-15 01:01:28 | Re: Postgres crashes at memcopy() after upgrade to PG 13. |
| Previous Message | Avinash Kumar | 2021-03-14 23:14:40 | Postgres crashes at memcopy() after upgrade to PG 13. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Julien Rouhaud | 2021-03-15 00:46:44 | Re: REINDEX backend filtering |
| Previous Message | Julien Rouhaud | 2021-03-15 00:35:51 | Re: REINDEX backend filtering |