From: | marcin mank <marcin(dot)mank(at)gmail(dot)com> |
---|---|
To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Streaming rep - why log shipping is necessary? |
Date: | 2010-02-25 08:55:08 |
Message-ID: | b1b9fac61002250055s6b53f9ecudc8d1d5f10f6366@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello,
I was reading the SR docs, and have the following question:
Is there a fundamental reason why archive_command etc. is required in
streaming replication mode?
Can`t setting up the standby be more like:
pg_start_streaming_backup() on the master (this will be queuing up
files in pg_xlog)
copy the data dir
set up the slave to connect to the master via streaming protocol
set up the master to allow connections from the slave
start slave (slave pulls the necessary WAL records from the master via
streaming, and signals the master that it`s done backing up)
When standby starts accepting connections, we know that the standby is OK.
archive_command, restore_command, etc. would be configured empty in this mode.
The failure mode for this is the pg_xlog directory filling up on the
master before the backup is done. But then, we can tell people to use
the more combersome, current setup.
Greetings
Marcin Mańk
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2010-02-25 09:08:23 | Re: Streaming rep - why log shipping is necessary? |
Previous Message | Heikki Linnakangas | 2010-02-25 08:10:13 | Re: testing cvs HEAD - HS/SR - xlog timeline 0 pg_xlogfile_name_offset |