From: | "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
---|---|
To: | "Erik Jones" <erik(at)myemma(dot)com> |
Cc: | "Postgres general mailing list" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Standby servers and incrementally updated backups |
Date: | 2007-06-25 20:40:43 |
Message-ID: | 1182804044.3625.19.camel@silverbirch.site |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, 2007-06-25 at 13:42 -0500, Erik Jones wrote:
> It is my understanding that once a standby server has reached the
> point where it is often waiting for wal files to replay, it is pretty
> much caught up to the primary server, with the differences being in
> whatever wal files are currently in queue to be archived by the
> primary.
Yes. You can tell by using
select pg_xlogfile_name(pg_current_xlog_location());
to see what the current file on the Primary is.
> If I'm correct, then for large databases wherein it can
> take hours to take a base backup, is there anything to be gained by
> using incrementally updated backups?
If you are certain there are parts of the database not touched at all
between backups. The only real way to be sure is to take file level
checksums, or you can trust file dates. Many backup solutions can do
this for you.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Talha Khan | 2007-06-25 20:48:01 | Re: A problem in inheritance |
Previous Message | Michael Glaesemann | 2007-06-25 20:05:19 | Re: NO DATA FOUND Exception |