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 1hlCcG-0007U6-GC for pgsql-hackers@arkaria.postgresql.org; Wed, 10 Jul 2019 13:26:36 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hlCcF-00041C-Bz for pgsql-hackers@arkaria.postgresql.org; Wed, 10 Jul 2019 13:26:35 +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 1hlCcF-000415-2X for pgsql-hackers@lists.postgresql.org; Wed, 10 Jul 2019 13:26:35 +0000 Received: from mail-qt1-x843.google.com ([2607:f8b0:4864:20::843]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hlCcC-0004Co-E0 for pgsql-hackers@lists.postgresql.org; Wed, 10 Jul 2019 13:26:34 +0000 Received: by mail-qt1-x843.google.com with SMTP id z4so2379296qtc.3 for ; Wed, 10 Jul 2019 06:26:32 -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=s4hvCpnAaHvFquv3c1cj6cV2xkRy0/mMV1/qKBvvlwc=; b=pt+C4qZvx7P+4xHkZ2xulb1YgbBcPVzh99SotMiDenosEbff+rjAuLPfzBgMreWuZj CDjc3Ai3H6CFUoxP1625DCKuYQLN8gaWL++ZLWMgkOR2VHX2UaHZ0VetB8kupYCxHvH+ iJrJzdqI+VJWTgb3LEYrLIO4tXBtxVmY6wfODJd3jT6unrlv3flOHQcGserjHMFtjuo8 UqHop/T1Ygm+O70yn4xXTgXF98gNn7czFgxCnFcguEbLJpfmaHQeZDzYYxA3GPRHmGI5 efvmwbXQtQwCZiVDE81sFr2Qp1XpzxfqqA3fLRTHExvmYa2zSvEja3v3d32SA9JghuOy yoYw== 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=s4hvCpnAaHvFquv3c1cj6cV2xkRy0/mMV1/qKBvvlwc=; b=BMMXMVg1EWbKN5a0wTeIUq4+A/ImVTWC5QJaX3hvPfpfuVMp5eBMbxz92VzwKh3R4U n0rHrghnMpfiqaXzJhsN3BMedPpLKdTldIMx29DVgxafZJHByJMhOVdPX6nJCnX5k6qj 0MitJpYbSnhUtqV7APJHEiAWPEg9UvM1AP5VKEpEXzlL30pXbPpoufNjreh+QiZ0gjXB 2dHl+iBLkJKMjmptEHOavkWo+9LXYEPBMdBun377KNTgofdWQqAxrMDCIkU+jbQYjlR2 M9MWLlfTBSvoDsu+Q+ZnStTeG5JupIEOsWBprxQVI//ADEcO+rWpXnO49WEBq0XRaaAb fd6Q== X-Gm-Message-State: APjAAAW48ESLlF7ecZJMeNOTj82U+Xf0dUjnXWh78SF4xlnaTT99Fr8S eidHTYCapvQfc9098OVG/5yRBw== X-Google-Smtp-Source: APXvYqxg/MCQwWU7S07GbIQMpcvJcc2KRDy1+5EiWimRNvAxV9KIriDU/9SCydV+qcZ60CEe+cVZqA== X-Received: by 2002:aed:3742:: with SMTP id i60mr23420760qtb.376.1562765190955; Wed, 10 Jul 2019 06:26:30 -0700 (PDT) Received: from nimloth.alvh.no-ip.org ([190.121.29.3]) by smtp.gmail.com with ESMTPSA id g10sm961434qki.37.2019.07.10.06.26.30 (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Wed, 10 Jul 2019 06:26:30 -0700 (PDT) Received: by nimloth.alvh.no-ip.org (Postfix, from userid 1000) id F23BA121EBC; Wed, 10 Jul 2019 09:26:28 -0400 (-04) Date: Wed, 10 Jul 2019 09:26:28 -0400 From: Alvaro Herrera To: Robert Haas Cc: Tatsuro Yamada , PostgreSQL Hackers Subject: Re: progress report for ANALYZE Message-ID: <20190710132628.GA26281@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-Jul-10, Robert Haas wrote: > On Tue, Jul 9, 2019 at 6:12 PM Alvaro Herrera wrote: > > Hmm, ok. In CREATE INDEX, we use the block counters multiple times. > > Why do we do that? Because we scan the table first, then the index, then the table again (last two for the validation phase of CIC). We count "block numbers" separately for each of those, and keep those counters in the same pair of columns. I think we also do that for tuple counters in one case. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services