On Mon, Aug 6, 2012 at 3:29 AM, Ben Chobot be...@silentmedia.com wrote:
On Aug 5, 2012, at 11:12 AM, Fujii Masao wrote:
On Sat, Jul 28, 2012 at 2:00 AM, Ben Chobot be...@silentmedia.com wrote:
We make heavy use of streaming replication on PG 9.1 and it's been great for
us. We do have one
On Aug 7, 2012, at 9:32 AM, Fujii Masao wrote:
On Mon, Aug 6, 2012 at 3:29 AM, Ben Chobot be...@silentmedia.com wrote:
Oh, I would have though that doing a clean shutdown of the old master (step
1) would have made sure that all the unstreamed wal records would be flushed
to any connected
On Sun, Aug 5, 2012 at 10:12 PM, Fujii Masao masao.fu...@gmail.com wrote:
Have we just avoided running pg_basebackup, or have we just given ourselves
data corruption?
If you change your operations in the above-mentioned way, I think you can
avoid pg_basebackup on the planned switch. I've not
On Sat, Jul 28, 2012 at 2:00 AM, Ben Chobot be...@silentmedia.com wrote:
We make heavy use of streaming replication on PG 9.1 and it's been great for
us. We do have one issue with it, though, and that's when we switch master
nodes - currently, the documentation says that you must run
On Aug 5, 2012, at 11:12 AM, Fujii Masao wrote:
On Sat, Jul 28, 2012 at 2:00 AM, Ben Chobot be...@silentmedia.com wrote:
We make heavy use of streaming replication on PG 9.1 and it's been great for
us. We do have one issue with it, though, and that's when we switch master
nodes - currently,
Anybody?
On Jul 27, 2012, at 10:00 AM, Ben Chobot wrote:
We make heavy use of streaming replication on PG 9.1 and it's been great for
us. We do have one issue with it, though, and that's when we switch master
nodes - currently, the documentation says that you must run pg_basebackup on
We make heavy use of streaming replication on PG 9.1 and it's been great for
us. We do have one issue with it, though, and that's when we switch master
nodes - currently, the documentation says that you must run pg_basebackup on
your old master to turn it into a slave. That makes sense when the
