Skip site navigation (1) Skip section navigation (2)

WAL/PITR additional items

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: WAL/PITR additional items
Date: 2005-04-20 17:22:42
Message-ID: 1114017762.16721.2286.camel@localhost.localdomain (view raw or flat)
Thread:
Lists: pgsql-hackers
A range of WAL/PITR items still need work. I'm fairly sure I won't be
doing any of these in time for 8.1, so feel free to have a go.

1. PITR archive recovery could do more to overlap recovery of files, so
that recovery overall is faster. This is already possible by designing
your archive command to perform this buffering for you, but it may be a
good idea to build this directly into the recovery scheme.

2. PreallocXlogFiles to run from a separate process to make it
effective, as discussed last year. The most natural place to put it
would be the Archiver, though that is only present when archive_command
is set. That means we could have the bgwriter execute it every so often,
perhaps every 5 or 10 cycles to avoid lock contention.

3. If PreallocXlogFiles becomes effective, it should be possible to turn
a pg_xlog directory out of space PANIC into a checkpoint to recycle
outstanding WAL files, then retry the prealloc. If that helps then reset
checkpoint_segments (and issue a WARNING to say it has happened) so that
the out of space condition is not encountered again. 

4. CRC reduction to CRC-32, plus hardware tuning. I'll stay in touch
with that in case we have further information to tune the assembler.

5. WAL archive compression

6. xlog.c refactoring into two pieces: WAL writing and WAL recovery

Best Regards, Simon Riggs


Responses

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2005-04-20 17:23:02
Subject: Re: [GENERAL] Idea for the statistics collector
Previous:From: Stephen FrostDate: 2005-04-20 16:50:55
Subject: Postgres: pg_hba.conf, md5, pg_shadow, encrypted passwords

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group