Hi Satish,
SELECT pg_current_xlog_location(); command is applicable from 8.4 version and select pg_last_xlog_receive_location(); command is applicable from 9.0 version.
select now() - pg_last_xact_replay_timestamp(); command is applicable from 9.1 version.
Monitoring Streaming replication:
For monitoring purpose, you can use the pg_controldata command. pg_controldata command will give you the information checkpoint lagging status of Standby Server.
/usr/pgsql-9.1/bin/pg_controldata <primary_data_dir>
/usr/pgsql-9.1/bin/pg_controldata <standby_data_dir>
Above command will return the exact status of replication between servers with below details.
Latest checkpoint location:
Prior checkpoint location:
Latest checkpoint's REDO location:
As per definition of Hot Standby, its a method of redundancy in which primary and secondary (Backup Server) runs simultaneously. The data is mirrored to secondary so that both should contain identical data in real time. With this user, would be able to execute the Query against Database while secondary is in archive recovery mode.
This is what introduce in PG9.0. In-built Hot Standby.
You can use below link where you can refer about Hot Standby.
On Sat, May 31, 2014 at 3:34 PM, Satish K Biradar <satishbiradar1984@xxxxxxxxx> wrote:
Hi Kapil,
Thanks very much for your valuable time, explaining me in detail.
Could you please tell me whether these commands applicable to 8.4, what are
the versions that these commands are compatible. And one more thing would
you please provide me some information regarding hot standby (what are the
versions it is compatible, and useful views to check the status of hot
standby)
Appreciate your patience.
Thanks,
Satish K.
--
View this message in context: http://postgresql.1045698.n5.nabble.com/Archive-views-tp5805521p5805651.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
