On Sun, 2011-08-21 at 08:04 -0700, alexondi wrote:
> But still, how to do it (check server state) in this case?
>
pg_controldata is probably a good solution. Or checking process titles
with "ps -ef".
--
Guillaume
http://blog.guillaume.lelarge.info
http://www.dalibo.com
--
Sent via pgsql
But still, how to do it (check server state) in this case?
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/Streaming-replication-without-hot-standby-tp4719918p4720634.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
--
Sent via pgsql-general m
On Sun, Aug 21, 2011 at 11:12 AM, alexondi wrote:
> So, how can I check is the slave-server up and properly work (recovery is in
> progress) in this case?
> Check the log for some messages?
It's certainly more tricky...
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL
So, how can I check is the slave-server up and properly work (recovery is in
progress) in this case?
Check the log for some messages?
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/Streaming-replication-without-hot-standby-tp4719918p4720156.html
Sent from the PostgreSQL
On Sun, 2011-08-21 at 00:19 -0700, alexondi wrote:
> Hi!
> If I use streaming replication must I setup hot stanby mode on my
> slave-server?
No, you don't have to.
> If not then this server would not accept any connections?
>
Exactly. Except the streaming one.
--
Guillaume
http://blog.guil
Hi!
If I use streaming replication must I setup hot stanby mode on my
slave-server?
If not then this server would not accept any connections?
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/Streaming-replication-without-hot-standby-tp4719918p4719918.html
Sent from the Po
