Re: pg16: invalid page/page verification failed

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Justin Pryzby <pryzby(at)telsasoft(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, Andres Freund <andres(at)anarazel(dot)de>
Subject: Re: pg16: invalid page/page verification failed
Date: 2023-10-06 00:20:05
Message-ID: ZR9StfAmBdTqPDdt@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Oct 05, 2023 at 11:45:18AM -0500, Justin Pryzby wrote:
> This table is what it sounds like: a partition into which CSV logs are
> COPY'ed. It would've been created around 8am. There's no special
> params set for the table nor for autovacuum.

This may be an important bit of information. 31966b151e6a is new as
of Postgres 16, has changed the way relations are extended and COPY
was one area touched. I am adding Andres in CC.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Krishnakumar R 2023-10-06 00:24:21 Re: Move bki file pre-processing from initdb to bootstrap
Previous Message Michael Paquier 2023-10-06 00:09:10 Re: Add a new BGWORKER_BYPASS_ROLELOGINCHECK flag