On 05/28/2014 06:41 PM, Andres Freund wrote:
Hi,
Pushed a fix for it. I am pretty sure it will, but could you still test
that it fixes your problem?
Thanks!
The fix seems to work (I am no longer getting the timeout on slot creation)
Thanks
Andres Freund
--
Sent via pgsql-hackers
Hi,
On 2014-05-17 01:34:25 +0200, Andres Freund wrote:
On 2014-05-16 17:02:33 -0400, Steve Singer wrote:
I don't think that's going to cut it though. The creation can take
longer than whatever wal_sender_timeout is set to (when there's lots of
longrunning transactions). I think checking
I am finding that my logical walsender connections are being terminated
due to a timeout on the CREATE REPLICATION SLOT command. with
terminating walsender process due to replication timeout
Below is the stack trace when this happens
#3 0x0067df28 in WalSndCheckTimeOut
Hi,
On 2014-05-16 16:37:16 -0400, Steve Singer wrote:
I am finding that my logical walsender connections are being terminated due
to a timeout on the CREATE REPLICATION SLOT command. with terminating
walsender process due to replication timeout
Below is the stack trace when this happens
On 05/16/2014 04:43 PM, Andres Freund wrote:
Hi,
I don't think that's going to cut it though. The creation can take
longer than whatever wal_sender_timeout is set to (when there's lots of
longrunning transactions). I think checking whether last_reply_timestamp
= 0 during timeout checking is
On 2014-05-16 17:02:33 -0400, Steve Singer wrote:
I don't think that's going to cut it though. The creation can take
longer than whatever wal_sender_timeout is set to (when there's lots of
longrunning transactions). I think checking whether last_reply_timestamp
= 0 during timeout checking is
