Postgres Pro
Downloads
Home   >   mailing lists

Re: progress report for ANALYZE - Mailing list pgsql-hackers

From Robert Haas
Subject Re: progress report for ANALYZE
Date
Msg-id CA+TgmoYFxXTaQErccaV+z6+kuNDFY64H+eDRPXkyh_JG=uZArQ@mail.gmail.com
Whole thread Raw
In response to Re: progress report for ANALYZE  (Tatsuro Yamada <tatsuro.yamada.tf@nttcom.co.jp>)
Responses Re: progress report for ANALYZE  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
Tree view 
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.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-hackers by date:

Previous
From: Alexander Korotkov
Date:
Subject: Re: [PATCH] kNN for btree
Next
From: Tomas Vondra
Date:
Subject: Re: Multivariate MCV list vs. statistics target