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 1k7kUM-0005Bx-ON for pgsql-hackers@arkaria.postgresql.org; Mon, 17 Aug 2020 19:08: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 1k7kUL-0004bT-F3 for pgsql-hackers@arkaria.postgresql.org; Mon, 17 Aug 2020 19:08:09 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1k7kUL-0004bM-3C for pgsql-hackers@lists.postgresql.org; Mon, 17 Aug 2020 19:08:09 +0000 Received: from mail-qk1-x741.google.com ([2607:f8b0:4864:20::741]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1k7kUG-0001Yx-Bo for pgsql-hackers@lists.postgresql.org; Mon, 17 Aug 2020 19:08:06 +0000 Received: by mail-qk1-x741.google.com with SMTP id m7so15963784qki.12 for ; Mon, 17 Aug 2020 12:08:03 -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=8lzIWtT39hubrvZK7sNi1Dzg10EmaDHCKNHhlFOOHoo=; b=QkKt1aAINlH89evCI8mfh25LEOOFDHh+2G6doVEKZaVXLBReGP4NZgZCC5ofSRzX3p F8tO+HnQHftOCHI4iJktlc7eDRKdmHCul+kJgJCVUbuf5xzhK11G4AzrqoGafDECJUf4 fh5tMeaOsc/qsP/OzHZM03uhW46j3HyVvfAfDU4Gv6oySRIQswRVqVpOamacbmWC2PER xWZJ/4d1485I8iqixXXDGTQdqYaqChmHukKvznRdIEos0PCGcixDz9RHPS8NzSoAm6yG VLcmanM/eZ1G1qjxtgoohGp3/XKL+BNpUIL7slPKcOc5B3YXdvnz8EBT8P2GgbQzptIg 8lOA== 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=8lzIWtT39hubrvZK7sNi1Dzg10EmaDHCKNHhlFOOHoo=; b=dzGb12KnO2W6Szci8gSUYmefdIMYurgOzqJEDp1Wq6+YFIQgoYI6wpIxHyIQGs00m1 cOu2m0IoCooHvdw+sGnxPMfNGV2GI80PVlSJYxiS80sJYsTvQIb/lc9BbcB8ZLBq0sFe lGQQIjMMNxk/5EjMTi4liVgqGjmeuD2J3xeg3z6H7Rf3vcCLzEflaOiwK5Lb7LTpFKox PH1iXSNdCcjJoT6l5GuGjnNUTHrqqq/XimCJvNeGr4P9XAVKoqRMCMD5UU33ZAwZQ91p BBKb7NZl9SmsoOLppK3zpZbHoiTJOJRupULGWakryf6f2SbrW6K4JEwwMwCZPfUEm0Wq g10g== X-Gm-Message-State: AOAM531z0YA65Hmrm4g5FZaios6q3XYd5i8UFBbwnJUmRw9sr+T/Tqjt kv/f69Se8XBhJeycpFwgFlp73+V0bxqRTm4Qc6yHKK8wnMUp6CMq5g5L8W4/oh54uW6OmPOFzHL 31oBCM8Ep7GMNIaNITqD+ZTHIiqG+txKXGEI8g2+W0YeDgLjyJgKMq11RuSgpu5SA7JNIS2xHbT DYvmGKTf5F1hLFa9QH X-Google-Smtp-Source: ABdhPJxHr5ILUCGCWipX+qWNFn0/XdlfKpayQy/YWR3l78KjN9HijV0uJ48Z9g8Mjb+pJwViMs8L3g== X-Received: by 2002:a37:b502:: with SMTP id e2mr14619805qkf.144.1597691281371; Mon, 17 Aug 2020 12:08:01 -0700 (PDT) Received: from perhan.alvh.no-ip.org ([190.95.19.47]) by smtp.gmail.com with ESMTPSA id i65sm18228455qkf.126.2020.08.17.12.08.00 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 17 Aug 2020 12:08:00 -0700 (PDT) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id B703D2A151A; Mon, 17 Aug 2020 15:07:58 -0400 (-04) Date: Mon, 17 Aug 2020 15:07:58 -0400 From: Alvaro Herrera To: Tom Lane Cc: Anastasia Lubennikova , PostgreSQL Hackers Subject: Re: [BUG] Error in BRIN summarization Message-ID: <20200817190758.GA31235@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <871534.1597503261@sss.pgh.pa.us> User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2020-Aug-15, Tom Lane wrote: > hyrax's latest report suggests that this patch has issues under > CLOBBER_CACHE_ALWAYS: > > https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=hyrax&dt=2020-08-13%2005%3A09%3A58 > > Hard to tell whether there's an actual bug there or just test instability, > but either way it needs to be resolved. 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. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services