Re: monitoring CREATE INDEX [CONCURRENTLY]
От | Robert Haas |
---|---|
Тема | Re: monitoring CREATE INDEX [CONCURRENTLY] |
Дата | |
Msg-id | CA+TgmoatvC9v2gBHOKtwdchaAfbDo1PiBxxqEzBEyCk65VR59Q@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: monitoring CREATE INDEX [CONCURRENTLY] (Alvaro Herrera <alvherre@2ndquadrant.com>) |
Ответы |
Re: monitoring CREATE INDEX [CONCURRENTLY]
|
Список | pgsql-hackers |
On Mon, Mar 11, 2019 at 3:43 PM Alvaro Herrera <alvherre@2ndquadrant.com> wrote: > > Huh. Well, that's another option, but then what do we do if the > > number of phases is not a constant? > > Well, why do we care? "Some phases might be skipped". It seems pretty confusing. I mean, in the case of the CLUSTER patch, you're either going to seq-scan the table or index-scan the table. Those are (at last check) reported using different phase numbers, but they are mutually exclusive. Generally, if you are going to do either foo -> bar -> baz -> quux or foo -> bletch -> quux, how many phases are there total? 5? 4? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: