From: | Michael Nolan <htfoot(at)gmail(dot)com> |
---|---|
To: | Greg Smith <greg(at)2ndquadrant(dot)com> |
Cc: | pgsql-docs(at)postgresql(dot)org |
Subject: | Re: Fwd: [GENERAL] 9.1.3: launching streaming replication |
Date: | 2012-04-04 15:18:26 |
Message-ID: | CAOzAqu+cKdRkEv=ynczgh9QagXRYQV7N31P0ThXrXPtvm3wTXA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-general |
On Tue, Apr 3, 2012 at 7:30 PM, Greg Smith <greg(at)2ndquadrant(dot)com> wrote:
> Mike already fixed the category problem himself. I just updated
> http://wiki.postgresql.org/wiki/Streaming_Replication so that it suggests
> users visit the official docs and tutorial on the wiki, since we can't just
> make Google unlike that page easily.
>
Greg, there's sort of an inconsistency between the developer-oriented
streaming replication page and the tutorial.
The streaming replication page says to copy the entire data directory,
which would include the WAL logs in the pg_xlog directory. The 5 minute
version in the binary replication tutorial skips that directory, the longer
one copies it separately, after the backup is complete, so that the slave
can perform any committed changes as part of syncing up with the master.
I assume that there is no harm in copying the pg_xlog directory in the 5
minute version, and it was left out as a time-saver. However, if the
master fails and the slave has to take over, wouldn't it need the pg_xlog
directory? If it hasn't been created, could that cause problems or would
the backend know to create it?
--
Mike Nolan
From | Date | Subject | |
---|---|---|---|
Next Message | Thom Brown | 2012-04-06 19:15:06 | ODBCng |
Previous Message | Greg Smith | 2012-04-03 23:30:27 | Re: Fwd: [GENERAL] 9.1.3: launching streaming replication |
From | Date | Subject | |
---|---|---|---|
Next Message | Eric.Kamradt | 2012-04-04 15:27:46 | Can postgres be configure for GSS/Kerberos authentication without a keyfile? |
Previous Message | Jon Nelson | 2012-04-04 15:14:58 | Re: views, queries, and locks |