Skip to content

P
Postgres FD Implementation
Commit 6c5ced15 authored by Bruce Momjian's avatar Bruce Momjian
Browse files
Options

doc: list unlogged tables as a non-durable option

parent 5db55c6b
Hide whitespace changes
Inline Side-by-side
Showing with 13 additions and 4 deletions
doc/src/sgml/perform.sgml
View file @ 6c5ced15
...@@ -1572,6 +1572,15 @@ SELECT * FROM x, y, a, b, c WHERE something AND somethingelse; ...@@ -1572,6 +1572,15 @@ SELECT * FROM x, y, a, b, c WHERE something AND somethingelse;
</para> </para>
</listitem> </listitem>
<listitem>
<para>
Turn off <xref linkend="guc-synchronous-commit">; there might be no
need to force <acronym>WAL</acronym> writes to disk on every
commit. This setting does risk transaction loss (though not data
corruption) in case of a crash of the <emphasis>database</>.
</para>
</listitem>
<listitem> <listitem>
<para> <para>
Turn off <xref linkend="guc-full-page-writes">; there is no need Turn off <xref linkend="guc-full-page-writes">; there is no need
...@@ -1590,12 +1599,12 @@ SELECT * FROM x, y, a, b, c WHERE something AND somethingelse; ...@@ -1590,12 +1599,12 @@ SELECT * FROM x, y, a, b, c WHERE something AND somethingelse;
<listitem> <listitem>
<para> <para>
Turn off <xref linkend="guc-synchronous-commit">; there might be no Create <link linkend="SQL-CREATETABLE-UNLOGGED">unlogged
need to write the <acronym>WAL</acronym> to disk on every tables</link> to avoid <acronym>WAL</acronym> writes, though it
commit. This setting does risk transaction loss (though not data makes the tables non-crash-safe.
corruption) in case of a crash of the <emphasis>database</> alone.
</para> </para>
</listitem> </listitem>
</itemizedlist> </itemizedlist>
</para> </para>
</sect1> </sect1>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment