mirror of
https://github.com/postgres/postgres.git
synced 2026-05-26 03:11:44 -04:00
doc: Clarify CHECKPOINT handling of unlogged buffers
The CHECKPOINT reference page still described checkpoints as flushing all data files, which could be misleading as it depends on the value of FLUSH_UNLOGGED option. Update the description to make it clearer that only data files of permanent relations are flushed by default. Author: Chao Li <lic@highgo.com> Reviewed-by: Daniel Gustafsson <daniel@yesql.se> Discussion: https://postgr.es/m/4855807D-F1CA-44E6-9B58-406691832848@gmail.com
This commit is contained in:
parent
7e5d8bd013
commit
377cc45194
1 changed files with 4 additions and 2 deletions
|
|
@ -35,8 +35,10 @@ CHECKPOINT [ ( option [, ...] ) ]
|
|||
|
||||
<para>
|
||||
A checkpoint is a point in the write-ahead log sequence at which
|
||||
all data files have been updated to reflect the information in the
|
||||
log. All data files will be flushed to disk. Refer to
|
||||
all data files for permanent relations have been updated to reflect the
|
||||
information in the log. All data for permanent relations files will be
|
||||
flushed to disk, dirty buffers of unlogged relations are not flushed unless
|
||||
<literal>FLUSH_UNLOGGED</literal> is specified. Refer to
|
||||
<xref linkend="wal-configuration"/> for more details about what happens
|
||||
during a checkpoint.
|
||||
</para>
|
||||
|
|
|
|||
Loading…
Reference in a new issue