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

From Robert Haas
Subject Re: progress report for ANALYZE
Date
Msg-id CA+Tgmob_YTDVU=Z9CmQj6uP6hcuY77Bs1YFT+fy0Ayc6_Qzn1Q@mail.gmail.com
Whole thread Raw
In response to Re: progress report for ANALYZE  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: progress report for ANALYZE  (Julien Rouhaud <rjuju123@gmail.com>)
Re: progress report for ANALYZE  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
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.

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



pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: [Proposal] Table-level Transparent Data Encryption (TDE) and KeyManagement Service (KMS)
Next
From: Julien Rouhaud
Date:
Subject: Re: progress report for ANALYZE