mirror of
https://github.com/postgres/postgres.git
synced 2025-09-02 04:21:28 +03:00
Optionally prefetch referenced data in recovery.
Introduce a new GUC recovery_prefetch, disabled by default. When enabled, look ahead in the WAL and try to initiate asynchronous reading of referenced data blocks that are not yet cached in our buffer pool. For now, this is done with posix_fadvise(), which has several caveats. Better mechanisms will follow in later work on the I/O subsystem. The GUC maintenance_io_concurrency is used to limit the number of concurrent I/Os we allow ourselves to initiate, based on pessimistic heuristics used to infer that I/Os have begun and completed. The GUC wal_decode_buffer_size is used to limit the maximum distance we are prepared to read ahead in the WAL to find uncached blocks. Reviewed-by: Alvaro Herrera <alvherre@2ndquadrant.com> (parts) Reviewed-by: Andres Freund <andres@anarazel.de> (parts) Reviewed-by: Tomas Vondra <tomas.vondra@2ndquadrant.com> (parts) Tested-by: Tomas Vondra <tomas.vondra@2ndquadrant.com> Tested-by: Jakub Wartak <Jakub.Wartak@tomtom.com> Tested-by: Dmitry Dolgov <9erthalion6@gmail.com> Tested-by: Sait Talha Nisanci <Sait.Nisanci@microsoft.com> Discussion: https://postgr.es/m/CA%2BhUKGJ4VJN8ttxScUFM8dOKX0BrBiboo5uz1cq%3DAovOddfHpA%40mail.gmail.com
This commit is contained in:
@@ -803,6 +803,23 @@
|
||||
counted as <literal>wal_write</literal> and <literal>wal_sync</literal>
|
||||
in <structname>pg_stat_wal</structname>, respectively.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The <xref linkend="guc-recovery-prefetch"/> parameter can
|
||||
be used to improve I/O performance during recovery by instructing
|
||||
<productname>PostgreSQL</productname> to initiate reads
|
||||
of disk blocks that will soon be needed but are not currently in
|
||||
<productname>PostgreSQL</productname>'s buffer pool.
|
||||
The <xref linkend="guc-maintenance-io-concurrency"/> and
|
||||
<xref linkend="guc-wal-decode-buffer-size"/> settings limit prefetching
|
||||
concurrency and distance, respectively. The
|
||||
prefetching mechanism is most likely to be effective on systems
|
||||
with <varname>full_page_writes</varname> set to
|
||||
<varname>off</varname> (where that is safe), and where the working
|
||||
set is larger than RAM. By default, prefetching in recovery is enabled
|
||||
on operating systems that have <function>posix_fadvise</function>
|
||||
support.
|
||||
</para>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="wal-internals">
|
||||
|
Reference in New Issue
Block a user