public inbox for [email protected]
help / color / mirror / Atom feedFrom: Bruce Momjian <[email protected]>
To: PostgreSQL-documentation <[email protected]>
Subject: Re: mention of unlogged tables
Date: Mon, 24 Mar 2014 22:05:21 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
List-Unsubscribe: <mailto:[email protected]?body=unsub%20pgsql-docs>
On Fri, Dec 20, 2013 at 01:58:00PM -0500, Bruce Momjian wrote:
> Is there a reason we don't mention unlogged tables in our Non-Durable
> Settings docs section?
>
> http://www.postgresql.org/docs/devel/static/non-durability.html
I have applied the attached patch to mention unlogged tables in our
non-durable doc section; I also reordered the items.
--
Bruce Momjian <[email protected]> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
--
Sent via pgsql-docs mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
Attachments:
[text/x-diff] unlogged.diff (1.6K, 2-unlogged.diff)
download | inline diff:
diff --git a/doc/src/sgml/perform.sgml b/doc/src/sgml/perform.sgml
new file mode 100644
index 482490b..f0ab440
*** a/doc/src/sgml/perform.sgml
--- b/doc/src/sgml/perform.sgml
*************** SELECT * FROM x, y, a, b, c WHERE someth
*** 1574,1579 ****
--- 1574,1588 ----
<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>
+ <para>
Turn off <xref linkend="guc-full-page-writes">; there is no need
to guard against partial page writes.
</para>
*************** SELECT * FROM x, y, a, b, c WHERE someth
*** 1590,1601 ****
<listitem>
<para>
! Turn off <xref linkend="guc-synchronous-commit">; there might be no
! need to write the <acronym>WAL</acronym> to disk on every
! commit. This setting does risk transaction loss (though not data
! corruption) in case of a crash of the <emphasis>database</> alone.
</para>
</listitem>
</itemizedlist>
</para>
</sect1>
--- 1599,1610 ----
<listitem>
<para>
! Create <link linkend="SQL-CREATETABLE-UNLOGGED">unlogged
! tables</link> to avoid <acronym>WAL</acronym> writes, though it
! makes the tables non-crash-safe.
</para>
</listitem>
+
</itemizedlist>
</para>
</sect1>
view thread (2+ messages)
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected]
Subject: Re: mention of unlogged tables
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox