pgsql: Add: > > * Allow control over which tables are WAL-logged > >

From: momjian(at)postgresql(dot)org (Bruce Momjian)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Add: > > * Allow control over which tables are WAL-logged > >
Date: 2006-01-05 16:23:49
Message-ID: 20060105162349.1BA159DC816@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
Add:

>
> * Allow control over which tables are WAL-logged
>
> 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]

Modified Files:
--------------
pgsql/doc:
TODO (r1.1742 -> r1.1743)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1742&r2=1.1743)
pgsql/doc/src/FAQ:
TODO.html (r1.247 -> r1.248)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/TODO.html.diff?r1=1.247&r2=1.248)

Browse pgsql-committers by date

  From Date Subject
Next Message Bruce Momjian 2006-01-05 16:26:50 pgsql: Update wording: < the table.
Previous Message Bruce Momjian 2006-01-05 15:56:54 pgsql: Update x86 Solaris documenation ideas.