Re: Dividing progress/debug information in pg_standby, and stat before copy - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: Dividing progress/debug information in pg_standby, and stat before copy
Date
Msg-id [email protected]
Whole thread Raw
In response to Re: Dividing progress/debug information in pg_standby, and stat before copy  (Dimitri Fontaine <[email protected]>)
List pgsql-hackers
Dimitri Fontaine wrote:
> Heikki Linnakangas <[email protected]> writes:
>> Yes. Just like with pg_standby.
> 
> Hehe, I'm using walmgr.py from skytools instead, and this discussion
> makes me think I'll continue doing so even if using SR, as they are
> complementary solutions.
> 
> In SR mode, the master continues to archive as usual, and the slave will
> either take the WAL on a per-file basis from the restore_command or on
> an per-LSN basis from the walreceiver and a live connection to the
> master, right?

Right.

> Does it mean any working wal shipping setup (pitrtools, walmgr.py) will
> continue working unchanged, or should we begin testing those and
> scheduling adaptations to 9.0?

They will continue to work as is, just leave standby_mode=off. But if
you want to take advantage streaming replication, you'll have to switch
it to 'on', and adapt the scripts to work with that.

--  Heikki Linnakangas EnterpriseDB   http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Dividing progress/debug information in pg_standby, and stat before copy
Next
From: "David E. Wheeler"
Date:
Subject: Re: Review: listagg aggregate