Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commitc474585

Browse files
committed
Backpatch to 9.0 a doc mention that a BBU does not prevent partial page
writes.
1 parent554b00c commitc474585

File tree

1 file changed

+6
-4
lines changed

1 file changed

+6
-4
lines changed

‎doc/src/sgml/wal.sgml

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -167,10 +167,12 @@
167167
<productname>PostgreSQL</> periodically writes full page images to
168168
permanent WAL storage <emphasis>before</> modifying the actual page on
169169
disk. By doing this, during crash recovery <productname>PostgreSQL</> can
170-
restore partially-written pages from WAL. If you have a battery-backed disk
171-
controller or file-system software that prevents partial page writes
172-
(e.g., ZFS), you can safely turn off this page imaging by turning off the
173-
<xref linkend="guc-full-page-writes"> parameter.
170+
restore partially-written pages from WAL. If you have file-system software
171+
that prevents partial page writes (e.g., ZFS), you can turn off
172+
this page imaging by turning off the <xref
173+
linkend="guc-full-page-writes"> parameter. Battery-Backed Unit
174+
(BBU) disk controllers do not prevent partial page writes unless
175+
they guarantee that data is written to the BBU as full (8kB) pages.
174176
</para>
175177
</sect1>
176178

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp