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

Re: Streaming replication, and walsender during recovery

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Streaming replication, and walsender during recovery
Date: 2010-01-28 15:48:53
Message-ID: 15357.1264693733@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Fujii Masao <masao(dot)fujii(at)gmail(dot)com> writes:
> How about just making a restore_command copy the WAL files as the
> normal one (e.g., 0000...) instead of a pg_xlog/RECOVERYXLOG?
> Though we need to worry about deleting them, we can easily leave
> the task to the bgwriter.

The reason for doing it that way was to limit disk space usage during
a long restore.  I'm not convinced we can leave the task to the bgwriter
--- it shouldn't be deleting anything at that point.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Magnus HaganderDate: 2010-01-28 15:53:44
Subject: Re: pgsql: Define INADDR_NONE on Solaris when it's missing.
Previous:From: Tom LaneDate: 2010-01-28 15:46:47
Subject: Re: pgsql: Define INADDR_NONE on Solaris when it's missing.

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