Ah, great. I missed looking there.
Thanks.
On Sun, Sep 26, 2010 at 4:19 PM, Fujii Masao wrote:
> On Mon, Sep 27, 2010 at 7:46 AM, fazool mein wrote:
> > I checked the code for the keepalive feature. It seems that the socket
> > options are only set on the primary's socket connection. The tcp
>
On Mon, Sep 27, 2010 at 7:46 AM, fazool mein wrote:
> I checked the code for the keepalive feature. It seems that the socket
> options are only set on the primary's socket connection. The tcp connection
> created on the secondary for walreceiver does not use the keepalive
> parameters from the con
Hello again,
I checked the code for the keepalive feature. It seems that the socket
options are only set on the primary's socket connection. The tcp connection
created on the secondary for walreceiver does not use the keepalive
parameters from the configuration.
Am I correct? Is this intended or
Apologies. I'm new to Postgres and I didn't see that feature. It satisfies
what I want to do.
Thanks.
On Thu, Sep 16, 2010 at 7:34 PM, Fujii Masao wrote:
> On Fri, Sep 17, 2010 at 6:49 AM, fazool mein wrote:
> > I am designing a heartbeat system between replicas to know when a replica
> > goes
On Fri, Sep 17, 2010 at 6:49 AM, fazool mein wrote:
> I am designing a heartbeat system between replicas to know when a replica
> goes down so that necessary measures can be taken. As I see, there are two
> ways of doing it:
>
> 1) Creating a separate heartbeat process on replicas.
> 2) Creating a
Hello everyone,
I am designing a heartbeat system between replicas to know when a replica
goes down so that necessary measures can be taken. As I see, there are two
ways of doing it:
1) Creating a separate heartbeat process on replicas.
2) Creating a heartbeat message, and sending it over the con
