| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tatsuro Yamada <tatsuro(dot)yamada(dot)tf(at)nttcom(dot)co(dot)jp>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: progress report for ANALYZE |
| Date: | 2019-07-10 13:26:28 |
| Message-ID: | 20190710132628.GA26281@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2019-Jul-10, Robert Haas wrote:
> On Tue, Jul 9, 2019 at 6:12 PM Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2019-07-10 13:31:11 | Re: global / super barriers (for checksums) |
| Previous Message | Robert Haas | 2019-07-10 13:23:19 | Re: progress report for ANALYZE |