Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1czSll-0003oM-OX for pgsql-hackers@arkaria.postgresql.org; Sat, 15 Apr 2017 18:50:01 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1czSlk-0003EM-EC for pgsql-hackers@arkaria.postgresql.org; Sat, 15 Apr 2017 18:50:00 +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 1czSlh-0003D4-Vo for pgsql-hackers@postgresql.org; Sat, 15 Apr 2017 18:49:58 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1czSla-0007re-HT for pgsql-hackers@postgresql.org; Sat, 15 Apr 2017 18:49:57 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id v3FIngx8009859; Sat, 15 Apr 2017 14:49:42 -0400 From: Tom Lane To: Petr Jelinek cc: Andres Freund , Robert Haas , "pgsql-hackers@postgresql.org" , Peter Eisentraut Subject: Re: logical replication launcher crash on buildfarm In-reply-to: <65ecec21-1272-5c46-3c39-501a2298598e@2ndquadrant.com> References: <0471e978-b121-ad2f-2879-f1694d9a5ce7@2ndquadrant.com> <2124fb62-2393-8525-4fe9-b95b1b689d09@2ndquadrant.com> <09d8ad33-4287-a09b-a77f-77f8761adb5e@2ndquadrant.com> <8ebd3aa3-55eb-1106-7c10-7e7579f94582@2ndquadrant.com> <20170401021928.47zjjryhty5kdzqz@alap3.anarazel.de> <548f9c1d-eafa-e3fa-9da8-f0cc2f654e60@2ndquadrant.com> <5615.1492228914@sss.pgh.pa.us> <65ecec21-1272-5c46-3c39-501a2298598e@2ndquadrant.com> Comments: In-reply-to Petr Jelinek message dated "Sat, 15 Apr 2017 16:43:43 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <9857.1492282182.1@sss.pgh.pa.us> Date: Sat, 15 Apr 2017 14:49:42 -0400 Message-ID: <9858.1492282182@sss.pgh.pa.us> 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 Petr Jelinek writes: > On 15/04/17 06:01, Tom Lane wrote: >> I've had more than enough of seeing buildfarm failures from culicidae, >> so I whacked this around until I was happy with it and pushed it. >> Further adjustments welcome of course. > Thanks. Seems like culicidae is finally happy with master. Well, only sort of happy, but I see how we can fix that. >> I don't really understand why 9.6 needs a significantly different >> patch. AFAICS, it simply does not work (with any reliability) >> for a loadable module to call CreateParallelContext directly in 9.6. > I think the problem is that if somebody was using CreateParallelContext > it may have worked on unix when just normally forking if the extension > was loaded via shared_preload_libraries. And lot of extensions are linux > only. So we might break working setup for somebody if we change the > function signature. Ah, I didn't think of shared_preload_libraries. OK, we can't change the signature in released branches. > We may need to keep CreateParallelContext as is in back branches and add > some CreateParallelContextInternal which would do what > CreateParallelContext does in master (and is used by postgres) and then > make CreateParallelContextForExternalFunction simple wrapper around > that. It's somewhat ugly though. Yeah, but ugly compatibility hacks in back branches are pretty common. But rather than inventing "CreateParallelContextInternal", I suggest we just have the core code call CreateParallelContextForExternalFunction. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers