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

From Julien Rouhaud
Subject Re: progress report for ANALYZE
Date
Msg-id CAOBaU_aW3CTn-LJ9ZPicqWCHEowm0WyLnQoShLiiTLgtj3Ba0A@mail.gmail.com
Whole thread Raw
In response to Re: progress report for ANALYZE  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: progress report for ANALYZE  (Tatsuro Yamada <tatsuro.yamada.tf@nttcom.co.jp>)
List pgsql-hackers
On Mon, Jul 8, 2019 at 8:44 PM Robert Haas <robertmhaas@gmail.com> wrote:
>
> On Mon, Jul 8, 2019 at 2:18 PM Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
> > 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.
>
> I don't think I intended to make any such determination -- which
> commit do you think established this as the canonical behavior?
>
> I propose that once a field is set, we should leave it set until the end.

+1

Note that this patch is already behaving like that if the table only
contains dead rows.



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: progress report for ANALYZE
Next
From: Ashwin Agrawal
Date:
Subject: Re: Declared but no defined functions