| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | srinivas oguri <srinivasoguri7(at)gmail(dot)com>, pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: XX000: invalid BTree prefetch end_key |
| Date: | 2021-02-11 17:10:13 |
| Message-ID: | 1451720.1613063413@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Magnus Hagander <magnus(at)hagander(dot)net> writes:
> On Thu, Feb 11, 2021 at 5:01 PM srinivas oguri <srinivasoguri7(at)gmail(dot)com> wrote:
>> 2021-02-11 15:23:36 UTC:10.12.90.41(60874):@:[32120]:PANIC: XX000: invalid BTree prefetch end_key
>> 2021-02-11 15:23:36 UTC:10.12.90.41(60874):@:[32120]:LOCATION: _bt_prefetch_if_needed, nbtree.c:1255
> You need to send Aurora issues to AWS support, not to the PostgreSQL
> community. In particular, anything related to storage is very
> different in Aurora.
Indeed, neither the quoted message text nor the function
bt_prefetch_if_needed appear at all in community Postgres.
So this is definitely Aurora-specific.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Don Seiler | 2021-02-11 17:13:02 | Managing autovacuum freezing |
| Previous Message | Magnus Hagander | 2021-02-11 16:06:38 | Re: XX000: invalid BTree prefetch end_key |