Skip site navigation (1) Skip section navigation (2)

Re: WAL logging volume and CREATE TABLE

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: WAL logging volume and CREATE TABLE
Date: 2011-08-03 03:53:12
Message-ID: (view raw, whole thread or download thread mbox)
Lists: 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: 
 <item>CREATE INDEX</item>
 <item>CREATE TABLE AS</item>
 <item>COPY, when tables that were created or truncated in the same

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(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to


pgsql-hackers by date

Next:From: Dean RasheedDate: 2011-08-03 07:11:32
Subject: Re: cataloguing NOT NULL constraints
Previous:From: Alvaro HerreraDate: 2011-08-03 03:40:53
Subject: Re: cataloguing NOT NULL constraints

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group