Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cotFs-0002Ja-Il for pgsql-hackers@arkaria.postgresql.org; Fri, 17 Mar 2017 14:53:24 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cotFs-000092-5Q for pgsql-hackers@arkaria.postgresql.org; Fri, 17 Mar 2017 14:53:24 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cotEM-0003sd-Ck for pgsql-hackers@postgresql.org; Fri, 17 Mar 2017 14:51:50 +0000 Received: from mail-qt0-x229.google.com ([2607:f8b0:400d:c0d::229]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1cotEI-0001uE-WE for pgsql-hackers@postgresql.org; Fri, 17 Mar 2017 14:51:49 +0000 Received: by mail-qt0-x229.google.com with SMTP id n21so64441228qta.1 for ; Fri, 17 Mar 2017 07:51:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=from:subject:to:references:cc:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=UDXbg1x0ObWDqcm72Yi19Esm/4W8NPmm5QU+XTiozi8=; b=xnu052LlDgb0DErkaDeOkSFrYkwn+IH1zepQpt+6/6fh6fK81K560ybztGE91GQpBJ +pdMoHwaST0oETsN34sV6UCUnkYLY0nl0q714vZ8wpnjF605V2+Ji5X7Yq9BCclGjvHM /4+Pe4wOXIyUZBmKhhZ6G3AxI/23S/mYeDVANT6saly42Xw3tAhx3eTN93XeI97rkD5M Pzv6Iy1qwtz8al/bAL7dwoNHngIPW0AS3mYsZrouFcPAhJr6/GdgDA1yZKK71XIvRSFM KxLC7q3m1De+aluWt4Kv3xwY57aolBd/nowxjAvcH9AXZdLgR83jQsx4D/23LkAoK5uR Uq5w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:to:references:cc:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=UDXbg1x0ObWDqcm72Yi19Esm/4W8NPmm5QU+XTiozi8=; b=goiqDN/YNmtLM8RUOzJdQdHbtdPWgDr0wZEmLyPKnFtWT5+iv64KbL6yyfDJ3KWnV6 cuJ6ecfTZyiFEzJXexYlBHeYNybZiEzYIgKppIA8ckOEYHaqHhp3FwJRwZ35MjW4YQB7 S4cWD/6jg3MKGEuKRUmf57NC+Qu6nfWLH4cxUNXJm8WOu/089alhtAVqQCmEITlrqEJn Dm0oYPtPTZJvu1mXFP0/uGrEAE1tFDNzwtpK8gfsuZTQUshHtgeg+IBFmWqXxDjpmB4w R++G0eQPX3ZvgAtvl8unQuMf+8d9DwkbuIBWCy9KKZVv7gSvgTaTz2JB3IpZ5+8YusOU v8oQ== X-Gm-Message-State: AFeK/H06k28efzz0rgMjPuUUX94jr9q6LCCqhuzPKCzFcNcfGKdMkhUoNFFQQcolcQLtZE9vgUvLNOOCYdBlj/PGAJP+8kbSbCMbTsrRvbzcdJ1UcAceXGMOKSlcddNs6nUG8B1lPeh3CNgzkNYuTQxT7qv7Ysw7M1iEetYAzPs51Dw3Km6L2LX9JN5tDuScRW7YijS4abauZQI= X-Received: by 10.237.44.198 with SMTP id g64mr15827184qtd.87.1489762305189; Fri, 17 Mar 2017 07:51:45 -0700 (PDT) Received: from [192.168.10.146] ([98.122.164.227]) by smtp.gmail.com with ESMTPSA id d30sm6079286qtb.18.2017.03.17.07.51.44 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 17 Mar 2017 07:51:44 -0700 (PDT) From: Andrew Dunstan X-Google-Original-From: Andrew Dunstan Subject: Re: [COMMITTERS] pgsql: Use asynchronous connect API in libpqwalreceiver To: Peter Eisentraut , Petr Jelinek , Tom Lane References: <19403.1488586564@sss.pgh.pa.us> <34d98fbf-9195-04d2-b85a-634d6952ffdf@2ndquadrant.com> <19815.1488600693@sss.pgh.pa.us> <4144256b-dc4f-892c-a720-71f6e7b9ac87@2ndquadrant.com> <3ffe98f7-d2ed-65c6-51f3-4d97ffd6e312@2ndquadrant.com> Cc: pgsql-hackers@postgreSQL.org Message-ID: <34591606-976a-bbee-8eda-778c1e1fc52f@2ndQuadrant.com> Date: Fri, 17 Mar 2017 10:51:43 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org On 03/08/2017 08:29 PM, Andrew Dunstan wrote: > > On 03/08/2017 08:33 AM, Peter Eisentraut wrote: >> On 3/6/17 09:38, Peter Eisentraut wrote: >>> On 3/4/17 01:45, Petr Jelinek wrote: >>>> If that's the case, the attached should fix it, but I have no way of >>>> testing it on windows, I can only say that it still works on my machine >>>> so at least it hopefully does not make things worse. >>> Committed that. Let's see how it goes. >> So that didn't work. Now we probably need someone to dig into that host >> directly. >> >> Andrew, could you help? >> > > I'll take a look when I get a chance. Might be a few days. > I have confirmed on jacana Petr's observation that adding a timeout to the WaitLatchOrSocket cures the problem. cheers andrew -- Andrew Dunstan https://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers