pgsql: Update: > o Allow COPY on a newly-created table to skip WAL

From: momjian(at)svr1(dot)postgresql(dot)org (Bruce Momjian)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Update: > o Allow COPY on a newly-created table to skip WAL
Date: 2005-09-02 21:11:00
Message-ID: 20050902211100.2B1B0D8A1C@svr1.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
Update:

> o Allow COPY on a newly-created table to skip WAL logging
450a452,456
> On crash recovery, the table involved in the COPY would
> have its heap and index files truncated. One issue is
> that no other backend should be able to add to the table
> at the same time, which is something that is currently
> allowed.

Modified Files:
--------------
pgsql/doc:
TODO (r1.1651 -> r1.1652)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1651&r2=1.1652)
pgsql/doc/src/FAQ:
TODO.html (r1.158 -> r1.159)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/TODO.html.diff?r1=1.158&r2=1.159)

Browse pgsql-committers by date

  From Date Subject
Next Message Bruce Momjian 2005-09-02 21:23:05 pgsql: Update.
Previous Message Bruce Momjian 2005-09-02 21:01:21 pgsql: Update: < o Allow COPY into an empty table to skip WAL logging