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 1jKkd5-0008AU-RR for pgsql-hackers@arkaria.postgresql.org; Sat, 04 Apr 2020 15:22:39 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jKkd4-0000Y8-Ka for pgsql-hackers@arkaria.postgresql.org; Sat, 04 Apr 2020 15:22:38 +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 1jKkd4-0000Y1-Df for pgsql-hackers@lists.postgresql.org; Sat, 04 Apr 2020 15:22:38 +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 1jKkd1-0006kU-8O for pgsql-hackers@postgresql.org; Sat, 04 Apr 2020 15:22:37 +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 034FMWw3013138; Sat, 4 Apr 2020 11:22:32 -0400 From: Tom Lane To: Amit Langote cc: Petr Jelinek , Peter Eisentraut , Rafia Sabih , PostgreSQL-development Subject: Re: adding partitioned tables to publications In-reply-to: References: <4f999141-97c8-c968-a726-0a1ec3e36e47@2ndquadrant.com> <9684.1585929105@sss.pgh.pa.us> <13925.1585977907@sss.pgh.pa.us> <4f5a1798-9b23-f1fd-4b9e-67d0ea503e4c@2ndquadrant.com> Comments: In-reply-to Amit Langote message dated "Sat, 04 Apr 2020 23:43:44 +0900" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <13136.1586013752.1@sss.pgh.pa.us> Date: Sat, 04 Apr 2020 11:22:32 -0400 Message-ID: <13137.1586013752@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Amit Langote writes: > One thing to I must clarify: coverage for most of pgoutput.c looks > okay on each run. I am concerned that the coverage for the code added > by the patch is shown to be close to zero, which is a mystery to me, > because I can confirm by other means such as debugging elogs() to next > to the new code that the newly added tests do cover them. According to https://coverage.postgresql.org/src/backend/replication/pgoutput/index.html the coverage is pretty good. Maybe you're doing something wrong in enabling coverage testing locally? regards, tom lane