Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: avoiding WAL logging in 8.3
- From: "Simon Riggs" <simon(at)2ndquadrant(dot)com>
- To: "Tatsuo Ishii" <ishii(at)postgresql(dot)org>
- Cc: <pgsql-hackers(at)postgresql(dot)org>
- Subject: Re: avoiding WAL logging in 8.3
- Date: Tue, 24 Jul 2007 07:30:50 +0100
- Message-id: <1185258650(dot)4263(dot)32(dot)camel(at)ebony(dot)site>
On Tue, 2007-07-24 at 13:04 +0900, Tatsuo Ishii wrote: > I noticed in 8.3 there are chances where we can avoid WAL logging. For > example, 8.3's pgbench was modified to use TRUNCATE right before > COPY. Is there any documentation which describes that kind of > techniques? If there's none, I would volunteer the work to create such > a documentation since I think this is valuable information for DBAs > who wish to migrate to 8.3. The Performance Tips section has been modified to describe this. Would you like me to add something elsewhere also? Multiple entry points to information helps everybody, so I'll happily add more. -- Simon Riggs EnterpriseDB http://www.enterprisedb.com
- Follow-Ups:
- Re: avoiding WAL logging in 8.3
- From: Jim Nasby
- Re: avoiding WAL logging in 8.3
- From: Tatsuo Ishii
- Re: avoiding WAL logging in 8.3
- References:
- avoiding WAL logging in 8.3
- From: Tatsuo Ishii
- avoiding WAL logging in 8.3
- Prev by Date: Re: autovacuum default parameters
- Next by Date: Re: Reviewing new index types (was Re: [PATCHES]Updatedbitmap indexpatch)
- Previous by thread: avoiding WAL logging in 8.3
- Next by thread: Re: avoiding WAL logging in 8.3
- Indexes: