| 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> |
| Subject: | Re: Postgres crashes at memcopy() after upgrade to PG 13. |
| Date: | 2021-03-15 01:16:34 |
| Message-ID: | CA+hUKG+kaswjxn8+v5DuR5rCrGYGmKLyiqAXgX94wGEQhz333g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
[Dropping pgsql-general@ from the CC, because cross-posting triggers
moderation; sorry I didn't notice that on my first reply]
On Mon, Mar 15, 2021 at 2:05 PM Avinash Kumar
<avinash(dot)vallarapu(at)gmail(dot)com> wrote:
> On Sun, Mar 14, 2021 at 10:01 PM Avinash Kumar <avinash(dot)vallarapu(at)gmail(dot)com> wrote:
>> Also the datatype is bigint
Ok. Collation changes are the most common cause of index problems
when upgrading OSes, but here we can rule that out if your index is on
bigint. So it seems like this is some other kind of corruption in
your database, or a bug in the deduplication code.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Avinash Kumar | 2021-03-15 01:54:13 | Re: Postgres crashes at memcopy() after upgrade to PG 13. |
| Previous Message | Avinash Kumar | 2021-03-15 01:05:40 | Re: Postgres crashes at memcopy() after upgrade to PG 13. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2021-03-15 01:25:38 | Re: Collation versioning |
| Previous Message | Justin Pryzby | 2021-03-15 01:12:31 | Re: Different compression methods for FPI |