Re: WIP: WAL prefetch (another approach) - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: WIP: WAL prefetch (another approach)
Date
Msg-id CA+hUKG+5G1ptHSOfaY7Jk0rhyjnUxBqZDgjCHvLxfcR3_fHo+w@mail.gmail.com
Whole thread Raw
In response to Re: WIP: WAL prefetch (another approach)  (Tomas Vondra <tomas.vondra@2ndquadrant.com>)
List pgsql-hackers
On Sat, Jun 6, 2020 at 8:41 AM Tomas Vondra
<tomas.vondra@2ndquadrant.com> wrote:
> BTW in all three cases it happens right after the first restart point in
> the WAL stream:
>
>     LOG:  restored log file "0000000100000108000000FD" from archive
>     LOG:  restartpoint starting: time
>     LOG:  restored log file "0000000100000108000000FE" from archive
>     LOG:  restartpoint complete: wrote 236092 buffers (22.5%); 0 WAL ...
>     LOG:  recovery restart point at 108/FC000028
>     DETAIL:  Last completed transaction was at log time 2020-06-04
>              15:27:00.95139+02.
>     LOG:  recovery no longer prefetching: unexpected pageaddr
>           108/57000000 in log segment 0000000100000108000000FF, offset 0
>     LOG:  restored log file "0000000100000108000000FF" from archive
>
> It looks exactly like this in case of all 3 failures ...

Huh.  Thanks!  I'll try to reproduce this here.



pgsql-hackers by date:

Previous
From: Joe Conway
Date:
Subject: Re: repeat() function, CHECK_FOR_INTERRUPTS(), and unlikely()
Next
From: Alvaro Herrera
Date:
Subject: Re: Trouble with hashagg spill I/O pattern and costing