Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hEzuR-0002pF-LK for pgsql-hackers@arkaria.postgresql.org; Fri, 12 Apr 2019 17:24:15 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hEzuQ-0005Ju-7Y for pgsql-hackers@arkaria.postgresql.org; Fri, 12 Apr 2019 17:24:14 +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_SHA1:256) (Exim 4.89) (envelope-from ) id 1hEzuP-0005HG-QJ for pgsql-hackers@lists.postgresql.org; Fri, 12 Apr 2019 17:24:13 +0000 Received: from mail-qt1-x841.google.com ([2607:f8b0:4864:20::841]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hEzuM-0002mA-Lc for pgsql-hackers@lists.postgresql.org; Fri, 12 Apr 2019 17:24:13 +0000 Received: by mail-qt1-x841.google.com with SMTP id t28so12107065qte.6 for ; Fri, 12 Apr 2019 10:24:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=PGSLI081ahdDVmj25HifHwOZHSe5/Ek9CUF94JGimPE=; b=GDn27SfbaCh+aK1z2BHQJDCJLefQP4NJ1hB+d4ojZhHYKw3Rh8sxeDeWRYLQ4TZwg1 0woMkg/2F0DsmmzwmkHLFDDzXyy/TF88pPHj0fsTGxHJPeQ/XB1cs9gNWH9noO3qe2jq HHXEyukJPFy5JwXgDHVFmvrDl1zILvF0JqVpK4xJSJcqRWPWUZWigCw0qJMyzDMQ/9+o SCTaiRGnjaBcS7q4sEz3st0S/mgPxbWRvp7hNafbcPqGumAs1eD+Xcgg9GoIC5SmAllm YuqOCo5leSLZBXG61eFSuMrI5222oz/4pnuiaNBxh5V5EDMJ49FRvzbnXxm1GqDA3G0A D3eg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=PGSLI081ahdDVmj25HifHwOZHSe5/Ek9CUF94JGimPE=; b=hMQpH/qfi5fnShOoopgHPX8cihCPoDMbF9RXgnkVp8zF/2BP/I8WC6WXErLLphOB53 dqMjkeUtmqQhOtyH07rAyEBtUsOtdd0AVGOPVqW+z+sHXPFqWKiPB2LWEE6xdl/RRPlZ FsJ3+af6cHM6yParRqrxUPk+/Q2xWK9JYxjime+y2R+3XixpPGBZNPHFayhPRn8ft0mU Wu16STU4UzxFaavijnssdNNrK5pJOduTVKL8K8inFweW/ES4NZOGvf8K1kaMIgrs31iP li4OdAJGwzgYm79GUG1+x+j2dABgKdIfXLz1XUO6/OogCG00ab6jJJp5IFMMaLvLFaH9 Xo5w== X-Gm-Message-State: APjAAAWEPfEv/MtaqoYEwM4GwVxNOFhr774Fpmfo7Ji3Bh+hbmzzteNn bOtkCN2bUJPeVPmboQXU/+7dRA== X-Google-Smtp-Source: APXvYqyvNIW8sxNJDQp9paDq0rPDk2zl2Kd+LOoZthrkQkyt50YsQV1PKyUHsgNqW8NsZl/Qeo0gog== X-Received: by 2002:ac8:2ca3:: with SMTP id 32mr47164874qtw.60.1555089848985; Fri, 12 Apr 2019 10:24:08 -0700 (PDT) Received: from nimloth.alvh.no-ip.org ([190.121.29.3]) by smtp.gmail.com with ESMTPSA id 194sm18384329qkd.72.2019.04.12.10.24.08 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 12 Apr 2019 10:24:08 -0700 (PDT) Received: by nimloth.alvh.no-ip.org (Postfix, from userid 1000) id B2BBC120D9A; Fri, 12 Apr 2019 13:24:06 -0400 (-04) Date: Fri, 12 Apr 2019 13:24:06 -0400 From: Alvaro Herrera To: Peter Geoghegan Cc: Tom Lane , PostgreSQL Hackers Subject: Re: Reducing the runtime of the core regression tests Message-ID: <20190412172406.GA23214@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2019-Apr-12, Peter Geoghegan wrote: > On Fri, Apr 12, 2019 at 9:31 AM Alvaro Herrera wrote: > > Done. Do you have a preferred spot where the counts were wrong? > > Not really, but I can give you an example. > > Line counts for each of the two "break" statements within > _bt_keep_natts_fast() are exactly the same. I don't think that this > because we actually hit each break exactly the same number of times > (90,236 times). I think that we see this because the same instruction > is associated with both break statements in the loop. All of the > examples I've noticed are a bit like that. Not a huge problem, but > less useful than the alternative. Hmm, it's odd, because https://coverage.postgresql.org/src/backend/access/nbtree/nbtutils.c.gcov.html still shows that function doing that. pg_config shows: $ ./pg_config --configure '--enable-depend' '--enable-coverage' '--enable-tap-tests' '--enable-nls' '--with-python' '--with-perl' '--with-tcl' '--with-openssl' '--with-libxml' '--with-ldap' '--with-pam' 'CFLAGS=-O0' src/Makefile.global says: CFLAGS = -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement -Werror=vla -Wendif-labels -Wmissing-format-attribute -Wformat-security -fno-strict-aliasing -fwrapv -fexcess-precision=standard -fprofile-arcs -ftest-coverage -O0 the compile line for nbtutils is: gcc -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement -Werror=vla -Wendif-labels -Wmissing-format-attribute -Wformat-security -fno-strict-aliasing -fwrapv -fexcess-precision=standard -fprofile-arcs -ftest-coverage -O0 -I../../../../src/include -D_GNU_SOURCE -I/usr/include/libxml2 -c -o nbtutils.o nbtutils.c -MMD -MP -MF .deps/nbtutils.Po so I suppose there's something else that's affecting this. I wonder if it would be useful to add --enable-debug. I think I purposefully removed that, but I don't remember any details about it. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services