From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Tatsuro Yamada <tatsuro.yamada.tf@nttcom.co.jp>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: progress report for ANALYZE
Date: Mon, 8 Jul 2019 14:18:45 -0400
Message-ID: <20190708181845.GA14186@alvherre.pgsql> (raw)
In-Reply-To: <CA+TgmoYFxXTaQErccaV+z6+kuNDFY64H+eDRPXkyh_JG=uZArQ@mail.gmail.com>
On 2019-Jul-08, Robert Haas wrote:
> On Mon, Jul 8, 2019 at 5:29 AM Tatsuro Yamada
> <tatsuro.yamada.tf@nttcom.co.jp> wrote:
> > 17520|13599|postgres|16387|f|16387|scanning table|4425|4425
> > 17520|13599|postgres|16387|f|16387|analyzing sample|0|0
> > 17520|13599|postgres|16387|f|16387||0|0 <-- Is it Okay??
>
> Why do we zero out the block numbers when we switch phases? The
> CREATE INDEX progress reporting patch does that kind of thing too, and
> it seems like poor behavior to me.
Yeah, I got the impression that that was determined to be the desirable
behavior, so I made it do that, but I'm not really happy about it
either. We're not too late to change the CREATE INDEX behavior, but
let's discuss what is it that we want.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: alvherre@2ndquadrant.com, robertmhaas@gmail.com, tatsuro.yamada.tf@nttcom.co.jp, pgsql-hackers@lists.postgresql.org
Subject: Re: progress report for ANALYZE
In-Reply-To: <20190708181845.GA14186@alvherre.pgsql>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox