Postgres 7.1 features

From: "Schmidt, Peter" <peter(dot)schmidt(at)prismedia(dot)com>
To: "'pgsql-admin(at)postgresql(dot)org'" <pgsql-admin(at)postgresql(dot)org>
Subject: Postgres 7.1 features
Date: 2001-01-10 16:43:09
Message-ID: F1DC8388AD52D411B83B00D0B774D6EB19286A@winmail.prismedia.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

The 7.1 Release notes include the statement re WAL below.

"Write-ahead Log (WAL)
To maintain database consistency in case of an operating system crash,
previous releases of PostgreSQL have forced all data modifications to disk
before each transaction commit. With WAL, only one log file must be flushed
to disk, greatly improving performance. If you have been using -F in
previous releases to disable disk flushes, you may want to consider
discontinuing its use."

Have WAL changes had any impact on vacuum?

Are there other benefits gained from these changes? e.g. less likely to see
a corrupted database in the event of a system crash, performance gains, etc?

Where is the new WAL log - pg_log no longer exists?

Thanks for any and all comments.

Peter Schmidt
PRISMedia Networks, Inc.
pschmidt(at)prismedia(dot)com

Browse pgsql-admin by date

  From Date Subject
Next Message Peter Schmidt 2001-01-10 16:56:32 v7.1 & WAL
Previous Message D Johnson 2001-01-10 11:57:21 BAcking up a Postgres Database