From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
---|---|
To: | Ivann Ruiz <ivann(dot)jprog(at)gmail(dot)com> |
Cc: | PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Is my standby fully connected? |
Date: | 2015-06-01 18:04:26 |
Message-ID: | CAECtzeVyvHgqn+mz86xEoX25y7TM0CF9tOWb7FUrmw1LGX5XWA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi,
2015-06-01 19:57 GMT+02:00 Ivann Ruiz <ivann(dot)jprog(at)gmail(dot)com>:
> I just setup my databases and got this LOG:
>
> LOG: database system was shut down in recovery at 2015-06-01 13:31:21 EDT
> LOG: entering standby mode
> LOG: redo starts at 0/67000278
> LOG: consistent recovery state reached at 0/67000350
> LOG: record with zero length at 0/67000350
> LOG: database system is ready to accept read only connections
> LOG: started streaming WAL from primary at 0/67000000 on timeline 1
>
>
Sounds good to me.
> And it always stays like this, i never get a message like:
> LOG: streaming replication successfully connected to primary
>
> Additionally, i cannot run queries such as:
> psql -c "SELECT pg_current_xlog_location()" -h192.168.0.10
>
> ...to calculate replication lag, I get the following message:
> ERROR: recovery is in progress
> HINT: WAL control functions cannot be executed during recovery
>
> Can someone please tell me what is going on?
>
This is just what it's supposed to be. And it tells you exactly that. You
cannot use pg_current_xlog_location() on a slave.
Check pg_stat_replication view on the master.
--
Guillaume.
http://blog.guillaume.lelarge.info
http://www.dalibo.com
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2015-06-01 18:06:05 | Re: 9.4.1 -> 9.4.2 problem: could not access status of transaction 1 |
Previous Message | Ivann Ruiz | 2015-06-01 17:57:14 | Is my standby fully connected? |