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 1k7ld0-0008M6-Bw for pgsql-hackers@arkaria.postgresql.org; Mon, 17 Aug 2020 20:21:10 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1k7lcy-0001ZS-SB for pgsql-hackers@arkaria.postgresql.org; Mon, 17 Aug 2020 20:21:08 +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 1k7lcy-0001ZL-Ks for pgsql-hackers@lists.postgresql.org; Mon, 17 Aug 2020 20:21:08 +0000 Received: from mail-qt1-x835.google.com ([2607:f8b0:4864:20::835]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1k7lcv-0001IO-JX for pgsql-hackers@lists.postgresql.org; Mon, 17 Aug 2020 20:21:07 +0000 Received: by mail-qt1-x835.google.com with SMTP id w9so13455635qts.6 for ; Mon, 17 Aug 2020 13:21:05 -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=20kG3+bhxiFakEHdcjs0Tk1XiehWoAE67IAtP5GMvQY=; b=MuZRGr87/VMwFpUfUP07Be6nY4zbDE1XhEWysz5VNdB3YinSrFOp5n41xOvPIKeRNF j0EUnEIYrdKRL3jJQc0ztDB93QicEFjnJZHKtpMwEvrHfKriC0odrIggUEXgvxJ+wJnu 2ZLfQCEMiB+AEEOrXCuHvvM8lgo5RzpAXV3yF7BU4cqZFeez/QzebhR/4/tqChY+xsUk sfz85D9cPTjmkrRb0W+eaSBkjJlB0ya5P1tLg/d5Q7FA+TQzF/JHyIniqNN7RgbzDb9J 9R6h/u3Of3Azc1KC9WSvk0E9T71GK+h8LdSXgsaDmoZ61kcn44G4QkrlQMleZydaroC5 Tu7g== 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=20kG3+bhxiFakEHdcjs0Tk1XiehWoAE67IAtP5GMvQY=; b=oOX/Ft5/HgLnwvmLgOSrkD+ShpMiG12jRUS3IDvnLu7ToQ4OmwOBNEACEoi2UbFwfp 7/J/EwLXhSM5SX46Y9YrjKGDxj+ST5Hs9Lcu0pcm4kzw7GzOho95BFRDDgc3HqOYCFAh gkrBJb3ibogIyANNJof9czQPc8JT+41uBH3t4civGGlwRboVsDkxaH6zFNi4CaB+pSnk v0Pc6GTNXXsYclofKZnysrlsrgdQgoTPuX41iOGNGIP8KPmnflMIdkXEv3VhL+B9LVi0 xIF3jbK9JSBrRd+2qeLEA2wyJQ5DTArKim89X3eoA70EtV22Jr1dZ6KgKNsm/wTf+luF +qFw== X-Gm-Message-State: AOAM532fVXmnfRtqyORwtmO+e3qKvFTxKOac6AcoAtJXBzksG176CMuq ZPiYWKW46rWYPZOKb0dc9X9p4QkBMv/Cfcy/8YQfuRPiJqsOnJD/uIgmGXq8bPaKfytT8m3aeNS 09gqBFPJNLpnuyKMydLJNwijWlUa7z9986aEOspyjSWTOBW4jETrvynimusJu2iv0ocoEBX4IA1 nj20wlg171RsNYB6Wf X-Google-Smtp-Source: ABdhPJx8PnGbiCHcmmnM+FIQNxjl+rVg1MngXvhByfsctt9Dy1C3+9gIrNWdKzmODDphPybDCHh/nw== X-Received: by 2002:ac8:5546:: with SMTP id o6mr14421548qtr.211.1597695664465; Mon, 17 Aug 2020 13:21:04 -0700 (PDT) Received: from perhan.alvh.no-ip.org ([190.95.19.47]) by smtp.gmail.com with ESMTPSA id x198sm19761698qka.37.2020.08.17.13.21.03 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 17 Aug 2020 13:21:03 -0700 (PDT) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id DDDC72A151A; Mon, 17 Aug 2020 16:21:01 -0400 (-04) Date: Mon, 17 Aug 2020 16:21:01 -0400 From: Alvaro Herrera To: Tom Lane Cc: Anastasia Lubennikova , PostgreSQL Hackers Subject: Re: [BUG] Error in BRIN summarization Message-ID: <20200817202101.GA3895@alvherre.pgsql> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="WIyZ46R2i8wDzkSu" Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20200817190758.GA31235@alvherre.pgsql> User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --WIyZ46R2i8wDzkSu Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit On 2020-Aug-17, Alvaro Herrera wrote: > Hmm, the only explanation I can see for this is that autovacuum managed > to summarize the range before the test script did it. So the solution > would simply be to disable autovacuum for the table across the whole > script. > > I'm running the scripts and dependencies to verify that fix, but under > CLOBBER_CACHE_ALWAYS that takes quite a bit. I ran a subset of tests a few times, but was unable to reproduce the problem. I'll just push this to all branches and hope for the best. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services --WIyZ46R2i8wDzkSu Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="0001-Disable-autovacuum-for-BRIN-test-table.patch" From 6e70443edacfc86674995c0c10ade0aec7a4fddf Mon Sep 17 00:00:00 2001 From: Alvaro Herrera Date: Mon, 17 Aug 2020 16:20:06 -0400 Subject: [PATCH] Disable autovacuum for BRIN test table This should improve stability in the tests. Per buildfarm member hyrax (CLOBBER_CACHE_ALWAYS) via Tom Lane. Discussion: https://postgr.es/m/871534.1597503261@sss.pgh.pa.us --- src/test/regress/expected/brin.out | 2 +- src/test/regress/sql/brin.sql | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/test/regress/expected/brin.out b/src/test/regress/expected/brin.out index 0b14c73fc6..18403498df 100644 --- a/src/test/regress/expected/brin.out +++ b/src/test/regress/expected/brin.out @@ -26,7 +26,7 @@ CREATE TABLE brintest (byteacol bytea, int4rangecol int4range, lsncol pg_lsn, boxcol box -) WITH (fillfactor=10); +) WITH (fillfactor=10, autovacuum_enabled=off); INSERT INTO brintest SELECT repeat(stringu1, 8)::bytea, substr(stringu1, 1, 1)::"char", diff --git a/src/test/regress/sql/brin.sql b/src/test/regress/sql/brin.sql index 1289e76ecb..d1a82474f3 100644 --- a/src/test/regress/sql/brin.sql +++ b/src/test/regress/sql/brin.sql @@ -26,7 +26,7 @@ CREATE TABLE brintest (byteacol bytea, int4rangecol int4range, lsncol pg_lsn, boxcol box -) WITH (fillfactor=10); +) WITH (fillfactor=10, autovacuum_enabled=off); INSERT INTO brintest SELECT repeat(stringu1, 8)::bytea, -- 2.20.1 --WIyZ46R2i8wDzkSu--