Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1csg05-0001bC-18 for pgsql-hackers@arkaria.postgresql.org; Tue, 28 Mar 2017 01:32:45 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1csg04-00016V-FL for pgsql-hackers@arkaria.postgresql.org; Tue, 28 Mar 2017 01:32:44 +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 1csfyb-0006tX-1Y for pgsql-hackers@postgresql.org; Tue, 28 Mar 2017 01:31:13 +0000 Received: from mail-wr0-x22e.google.com ([2a00:1450:400c:c0c::22e]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1csfyS-0007mk-Tu for pgsql-hackers@postgresql.org; Tue, 28 Mar 2017 01:31:12 +0000 Received: by mail-wr0-x22e.google.com with SMTP id l43so81513710wre.1 for ; Mon, 27 Mar 2017 18:31:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=dexzk5b9n8mBbVAeR7s+ySDDCLKM/FEETvB5jKKCAhY=; b=C/cXcvaqhfjq81vHkRXnqdzDt8amfx5sv0OxQFg1iPfxe3Aaoyr4Mk5I31d3GduzEp yUDZnGiaLFJPVLzNj/luCnYeDAvzHjGI46wWQJN3UZu7I2/ndbEvpEUj3on6xpxyA+ZN 51TyAfDBa+dLfufG/nX5Tjg5lWPFHgmfsIKxve1f6Q+xvvvwn/yRpgVPqkhl0APuWRD3 9OUp0MWD4/cO2U38AXHpNhEtIbii1gTvanevI+rCmS7nUZfT7mOIjnWZ5aLlXLoZbzc/ O5SwCz7wyLhy3tOYXI242Q7j++2U487BpDtmHxjBqPzU3xKkYrRDeFIUP+xn0qNOSc0r lGLg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=dexzk5b9n8mBbVAeR7s+ySDDCLKM/FEETvB5jKKCAhY=; b=JI+xp6IuluaJUZWb6klOhhYuouL39vDuPKRLiNyeQwmQjMGEv3iIW9/Ly9lv6P/vcw Pm572R0LpYGXhn66rbgzr29m4D0qHtZbmaLw5gqA1+48Zauz/A1nLpWE4zmf6PkC6E5G 21hK7ZzOnmHjgWTr2OaEuBZGkU8SEfKs8JQcAx2/0WA60v6ZucByUvNB3xRTRZotlPXQ iIG7Kkrq+Ti6Rx84aCtRLWNBABS3FPOWBP0u80MAnwmGWtl8qSWrWkZcmQ1iwA1hoenh +Nh5edCqhb2GpqOF9NV3q1v8Jl3BCwxXxYTevOSYgSuQD9NlQIJsjd3au6ti4nbbcoJw bjoQ== X-Gm-Message-State: AFeK/H3nIz4Df50dRqh+rHQHzhjBiIfL1W5FyIhF23msO+C7iDX3xNH6vdDr8Eei5wWxYuPV X-Received: by 10.28.93.65 with SMTP id r62mr2234767wmb.77.1490664663998; Mon, 27 Mar 2017 18:31:03 -0700 (PDT) Received: from [192.168.0.105] (150.123.broadband11.iol.cz. [90.178.123.150]) by smtp.gmail.com with ESMTPSA id r17sm2724909wrc.47.2017.03.27.18.31.02 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 27 Mar 2017 18:31:03 -0700 (PDT) Subject: Re: logical replication launcher crash on buildfarm To: Robert Haas , Andres Freund References: <20170316032833.2zxfnqe3sl3ktrbt@alap3.anarazel.de> <20170316034246.3uurliezczmka6cn@alap3.anarazel.de> <20170316085322.crffknkgee5s6air@alap3.anarazel.de> <368e64f6-ee9a-f09f-82b4-a33b61b28d36@2ndquadrant.com> <20170327165023.t224nralrspk6udc@alap3.anarazel.de> Cc: "pgsql-hackers@postgresql.org" , Petr Jelinek , Peter Eisentraut From: Petr Jelinek Message-ID: <52d78669-0523-4e60-a263-841c96210256@2ndquadrant.com> Date: Tue, 28 Mar 2017 03:31:02 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -1.9 (-) 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 27/03/17 19:01, Robert Haas wrote: > On Mon, Mar 27, 2017 at 12:50 PM, Andres Freund wrote: >> Robert, Petr, either of you planning to fix this (as outlined elsewhere >> in the thred)? > > Oh, I didn't realize anybody was looking to me to fix this. I sort of > thought that it was fallout from the logical replication patch and > that Petr or Peter would deal with it. If that's not the case, I'm > not totally unwilling to take a whack at it, but I don't have much > personal enthusiasm for trying to figure out how to make dynamic > loading on the postgres binary itself work everywhere, so if it falls > to me to fix, it's likely to get a hard-coded check for some > hard-coded name. > It affects parallel workers same way, I'll write patch for HEAD soon, 9.6 probably with some delay. I'll expand the InternalBgWorkers thing that was added with logical replication to handle this in similar fashion how we do fmgrtab. -- Petr Jelinek http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, 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