Bruce Momjian <bruce(at)momjian(dot)us> writes:
>>> In minimal level, WAL-logging of some bulk operations, like CREATE
>>> INDEX, CLUSTER and COPY on a table that was created or truncated in the
>>> same transaction can be safely skipped, which can make those operations
>>> much faster (see Section 14.4.7).
> But the documentation states the WAL logging is reduced for CREATE INDEX
> by doing CREATE TABLE in the same transaction block. Why is this true?
It's not true, and it doesn't say that, or at least doesn't intend to
say that. That sentence is meant to be read as:
1. The optimization applies to CREATE INDEX.
2. The optimization applies to CLUSTER or COPY on a table that was
created or truncated in the current transaction.
I now see your point, which is that the sentence is easily misparsed.
regards, tom lane
In response to
pgsql-hackers by date
|Next:||From: Heikki Linnakangas||Date: 2011-08-02 15:59:24|
|Subject: Re: Hot standby and GiST page splits (was Re: WIP: Fast
GiST index build)|
|Previous:||From: Bruce Momjian||Date: 2011-08-02 15:32:57|
|Subject: Re: WAL logging volume and CREATE TABLE|