Re: [GENERAL] Archive# views

2014-06-02 Thread Satish K Biradar
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

Re: [GENERAL] Archive# views

2014-06-02 Thread Kapil Agarwal
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:*

[GENERAL] Archive# views

2014-05-30 Thread Satish K Biradar
Hello, I am a newbee to Postgresql and I want to build replication between master and slave servers(8.4). I was able to set it up but I cannot check archive# at master and slave servers as what was the last archive# generated at master and what is current archive# at Slave server that is being

Re: [GENERAL] Archive# views

2014-05-30 Thread Kapil Agarwal
Hi Satish, You can calculate the replication lag by comparing the current WAL write location on the primary with the last WAL location received/replayed by the standby. They can be retrieved using pg_current_xlog_location on the primary and the

Re: [GENERAL] Archive# views

2014-05-30 Thread Ray Stell
On May 30, 2014, at 6:19 PM, Kapil Agarwal wrote: Slave server: select pg_last_xlog_receive_location(); not possible back in 8.4. you could just compare the output of the pg_controldata command on both hosts.