Re: WIP: WAL prefetch (another approach)

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>
Cc: Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, David Steele <david(at)pgmasters(dot)net>, Andres Freund <andres(at)anarazel(dot)de>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: WIP: WAL prefetch (another approach)
Date: 2020-06-05 21:15:14
Message-ID: CA+hUKG+5G1ptHSOfaY7Jk0rhyjnUxBqZDgjCHvLxfcR3_fHo+w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Jun 6, 2020 at 8:41 AM Tomas Vondra
<tomas(dot)vondra(at)2ndquadrant(dot)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.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2020-06-05 21:19:43 Re: Trouble with hashagg spill I/O pattern and costing
Previous Message Joe Conway 2020-06-05 20:53:01 Re: repeat() function, CHECK_FOR_INTERRUPTS(), and unlikely()