Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jKbIx-0008U4-TX for pgsql-hackers@arkaria.postgresql.org; Sat, 04 Apr 2020 05:25:15 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jKbIw-0001He-DE for pgsql-hackers@arkaria.postgresql.org; Sat, 04 Apr 2020 05:25:14 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jKbIw-0001HX-6E for pgsql-hackers@lists.postgresql.org; Sat, 04 Apr 2020 05:25:14 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jKbIt-0002D6-9p for pgsql-hackers@postgresql.org; Sat, 04 Apr 2020 05:25:13 +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 0345P7G9013926; Sat, 4 Apr 2020 01:25:07 -0400 From: Tom Lane To: Petr Jelinek cc: Amit Langote , Peter Eisentraut , Rafia Sabih , PostgreSQL-development Subject: Re: adding partitioned tables to publications In-reply-to: <63961884-6d56-a12b-d3f5-9a5dcbcc37f4@2ndquadrant.com> References: <4f999141-97c8-c968-a726-0a1ec3e36e47@2ndquadrant.com> <44ecae53-98! 61-71b7-1d43-4658acc52519@2ndquadrant.com> <5183.1585925998@sss.pgh! .pa.us> <9684.1585929105@sss.pgh.pa.us> <63961884-6d56-a12b-d3f5-9a! 5dcbcc37f4@2ndquadrant.com> Comments: In-reply-to Petr Jelinek message dated "Sat, 04 Apr 2020 07:07:29 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <13924.1585977907.1@sss.pgh.pa.us> Date: Sat, 04 Apr 2020 01:25:07 -0400 Message-ID: <13925.1585977907@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Petr Jelinek writes: > On 03/04/2020 17:51, Tom Lane wrote: >> But the forked-off children have to write the gcov files independently, >> don't they? > Hmm that's very good point. I did see these missing coverage issue when > running tests that explicitly start more instances of postgres before > though. And with some quick googling, parallel testing seems to be issue > with gcov for more people. I poked around and found this: https://gcc.gnu.org/legacy-ml/gcc-help/2005-11/msg00074.html which says gcov instrumentation is multi-process safe, but not multi-thread safe. The multi-processing safety relies on OS level file locking, which is not available on some systems. That would explain why it works for me, but then there's a question of why it doesn't work for you ... regards, tom lane