From ef6d5b4e25178cb0e172b428a4e6d19abb1c4f5b Mon Sep 17 00:00:00 2001
From: Bruce Momjian
Date: Fri, 2 Sep 2005 21:10:59 +0000
Subject: [PATCH] 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.
---
doc/TODO | 9 +++++++--
doc/src/FAQ/TODO.html | 10 ++++++++--
2 files changed, 15 insertions(+), 4 deletions(-)
diff --git a/doc/TODO b/doc/TODO
index 2e0cd8a805..f7026afe22 100644
--- a/doc/TODO
+++ b/doc/TODO
@@ -2,7 +2,7 @@
PostgreSQL TODO List
====================
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
-Last updated: Fri Sep 2 17:01:18 EDT 2005
+Last updated: Fri Sep 2 17:10:58 EDT 2005
The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html.
@@ -389,7 +389,6 @@ SQL Commands
copy of db?
o Add ON COMMIT capability to CREATE TABLE AS ... SELECT
- o Allow COPY into an new table to skip WAL logging
* UPDATE
@@ -448,7 +447,13 @@ SQL Commands
processed, with ROLLBACK on COPY failure.
o %Have COPY return the number of rows loaded/unloaded?
+ o Allow COPY on a newly-created table to skip WAL logging
+ 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.
* GRANT/REVOKE
diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html
index 0b7aa3cef5..9fd764ee63 100644
--- a/doc/src/FAQ/TODO.html
+++ b/doc/src/FAQ/TODO.html
@@ -8,7 +8,7 @@
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
-Last updated: Fri Sep 2 17:01:18 EDT 2005
+Last updated: Fri Sep 2 17:10:58 EDT 2005
The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html.
@@ -355,7 +355,6 @@ first.
Use more reliable method for CREATE DATABASE to get a consistent
copy of db?
Add ON COMMIT capability to CREATE TABLE AS ... SELECT
- Allow COPY into an new table to skip WAL logging
UPDATE
@@ -407,6 +406,13 @@ first.
processed, with ROLLBACK on COPY failure.
%Have COPY return the number of rows loaded/unloaded?
+ Allow COPY on a newly-created table to skip WAL logging
+ 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.
+
GRANT/REVOKE