mirror/postgresql
2
0
Fork 0
mirror of https://git.postgresql.org/git/postgresql.git synced 2024-11-21 03:13:05 +08:00
Code Issues Packages Projects Releases Wiki Activity

Update wording:

Browse Source 
<   the table. Another option is to avoid transaction logging entirely
<   and truncate or drop the table on crash recovery.  These should be
<   implemented using ALTER TABLE, e.g. ALTER TABLE PERSISTENCE [ DROP |
<   TRUNCATE | STABLE | DEFAULT ].  [wallog]
>   the table.  This would affect COPY, and perhaps INSERT/UPDATE too.
>   Another option is to avoid transaction logging entirely and truncate
>   or drop the table on crash recovery.  These should be implemented
>   using ALTER TABLE, e.g. ALTER TABLE PERSISTENCE [ DROP | TRUNCATE |
>   STABLE | DEFAULT ].  [wallog]
This commit is contained in:
Bruce Momjian 2006-01-05 16:26:49 +00:00
parent 1b736817d0
commit e7893db5cf
2 changed files with 12 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
doc/TODO
View File

@ -2,7 +2,7 @@
PostgreSQL TODO List
====================
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
Last updated: Thu Jan 5 11:23:42 EST 2006
Last updated: Thu Jan 5 11:26:44 EST 2006
The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html.
@ -1019,10 +1019,11 @@ Write-Ahead Log
Allow tables to bypass WAL writes and just fsync() dirty pages on
commit. To do this, only a single writer can modify the table, and
writes must happen only on new pages. Readers can continue accessing
the table. Another option is to avoid transaction logging entirely
and truncate or drop the table on crash recovery. These should be
implemented using ALTER TABLE, e.g. ALTER TABLE PERSISTENCE [ DROP |
TRUNCATE | STABLE | DEFAULT ]. [wallog]
the table. This would affect COPY, and perhaps INSERT/UPDATE too.
Another option is to avoid transaction logging entirely and truncate
or drop the table on crash recovery. These should be implemented
using ALTER TABLE, e.g. ALTER TABLE PERSISTENCE [ DROP | TRUNCATE |
STABLE | DEFAULT ]. [wallog]
Optimizer / Executor

11
doc/src/FAQ/TODO.html
View File

@ -8,7 +8,7 @@
<body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF">
<h1><a name="section_1">PostgreSQL TODO List</a></h1>
<p>Current maintainer: Bruce Momjian (<a href="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/>
Last updated: Thu Jan 5 11:23:42 EST 2006
Last updated: Thu Jan 5 11:26:44 EST 2006
</p>
<p>The most recent version of this document can be viewed at<br/>
<a href="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>.
@ -923,10 +923,11 @@ first.
<p> Allow tables to bypass WAL writes and just fsync() dirty pages on
commit. To do this, only a single writer can modify the table, and
writes must happen only on new pages. Readers can continue accessing
the table. Another option is to avoid transaction logging entirely
and truncate or drop the table on crash recovery. These should be
implemented using ALTER TABLE, e.g. ALTER TABLE PERSISTENCE [ DROP |
TRUNCATE | STABLE | DEFAULT ]. [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?wallog">wallog</a>]
the table. This would affect COPY, and perhaps INSERT/UPDATE too.
Another option is to avoid transaction logging entirely and truncate
or drop the table on crash recovery. These should be implemented
using ALTER TABLE, e.g. ALTER TABLE PERSISTENCE [ DROP | TRUNCATE |
STABLE | DEFAULT ]. [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?wallog">wallog</a>]
</p>
</li></ul>
<h1><a name="section_20">Optimizer / Executor</a></h1>