From: | Matthew Kirkwood <matthew(at)hairy(dot)beasts(dot)org> |
---|---|
To: | <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Archived redo logs / Managed recovery mode? |
Date: | 2001-04-27 16:03:00 |
Message-ID: | Pine.LNX.4.33.0104271433390.24521-200000@sphinx.mythic-beasts.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
Firstly, the attached patch implements archiving of off-
line redo logs, via the wal_archive_dir GUC option. It
builds and appears to work (though it looks like guc-file.l
has some problems with unquoted strings containing slashes).
TODO: handle EXDEV from link/rename, and copy rather
than renaming.
Clearly this isn't a lot of use at the moment, but what I'd
really like would be a way to implement what our (Oracle)
DBA calls "managed recovery".
Essentially, the standby database is opened in read-only
mode (since PG seems to lack this, having it not open at
all should suffice :). and archived redo logs are copied
over from the live database (we do it via rsync, every 5
minutes) and rolled forward.
(Note: for what it's worth, we're using this because
Oracle's Advanced Replication is too unstable.)
Is there an easy way to do this? I suppose that while
there isn't a readonly option, it might be best done with
an external tool, not unlike resetxlog.
What are the plans for replication in 7.2 (assuming that
is what's next)? The rserv stuff looks neat, but rather
intricate. A cheap, out-of-band replication system would
make me very happy.
Matthew.
Attachment | Content-Type | Size |
---|---|---|
pg-archive.diff | text/plain | 3.6 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | The Hermit Hacker | 2001-04-27 16:44:09 | The new, the improved ... FTS Searching of Mailing List Archives |
Previous Message | Mike Mascari | 2001-04-27 15:46:47 | RE: Any optimizations to the join code in 7.1? |