| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
| Cc: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Can there ever be out of sequence WAL files? |
| Date: | 2022-01-17 07:15:30 |
| Message-ID: | YeUXkpwwv+E25gRm@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jan 12, 2022 at 12:23:00PM +0800, Julien Rouhaud wrote:
> On Wed, Jan 12, 2022 at 01:10:25PM +0900, Michael Paquier wrote:
>> xlog.c can be a good read to check the assumptions WAL replay relies
>> on, with things like CheckRecoveryConsistency() or
>> reachedConsistency.
>
> That should only stand for a WAL expected to be missing right? For something
> unexpected it should fail in XLogReadRecord() when trying to fetch a missing
> block?
Sure, as well as there are sanity checks related to invalid page
references when it comes to the consistency checks.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2022-01-17 07:34:44 | Re: Map WAL segment files on PMEM as WAL buffers |
| Previous Message | Michael Paquier | 2022-01-17 07:05:06 | Re: pg_dump/restore --no-tableam |