Re: WAL logging volume and CREATE TABLE - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: WAL logging volume and CREATE TABLE
Date
Msg-id 1312343425-sup-9110@alvh.no-ip.org
Whole thread Raw
In response to Re: WAL logging volume and CREATE TABLE  (Bruce Momjian <bruce@momjian.us>)
Responses Re: WAL logging volume and CREATE TABLE
List pgsql-hackers
Excerpts from Bruce Momjian's message of mar ago 02 22:46:55 -0400 2011:

> I have created a documentation patch to clarify this, and to mention
> CREATE TABLE AS which also has this optimization.

It doesn't seem particularly better to me.  How about something like

In minimal level, WAL-logging of some operations can be safely skipped,
which can make those operations much faster (see <blah>).  Operations on
which this optimization can be applied include: 
<simplelist><item>CREATE INDEX</item><item>CLUSTER</item><item>CREATE TABLE AS</item><item>COPY, when tables that were
createdor truncated in the sametransaction
 
</simplelist>

Minimal WAL does not contain enough information to reconstruct the data
from a base backup and the WAL logs, so either <literal>archive</> or
<literal>hot_standby</> level must be used to enable ...

-- 
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: cataloguing NOT NULL constraints
Next
From: Dean Rasheed
Date:
Subject: Re: cataloguing NOT NULL constraints