Re: BUG #17446: Suggest updating the section title "Building Indexes Concurrently"

Поиск
Список
Период
Сортировка
От David G. Johnston
Тема Re: BUG #17446: Suggest updating the section title "Building Indexes Concurrently"
Дата
Msg-id CAKFQuwaMhJXP1_n_-KfrjvqCJtG_M0NSqMCOxEQQqYhVoQZpoA@mail.gmail.com
обсуждение исходный текст
Ответ на BUG #17446: Suggest updating the section title "Building Indexes Concurrently"  (PG Bug reporting form <noreply@postgresql.org>)
Список pgsql-bugs
Дерево обсуждения
On Tue, Mar 22, 2022 at 4:19 PM PG Bug reporting form <noreply@postgresql.org> wrote:
The following bug has been logged on the website:

Bug reference:      17446
Logged by:          Troy Frericks
Email address:      troy@frericks.us
PostgreSQL version: 10.17
Operating system:   Documentation suggestion, ambiguous
Description:       

https://www.postgresql.org/docs/9.6/sql-createindex.html#SQL-CREATEINDEX-CONCURRENTLY

Suggest changing section title "Building Indexes Concurrently" to "Building
Indexes Using the CONCURRENTLY Parameter" to eliminate any ambiguity.

That seems worse.  If anything the title should answer the question "Concurrent with What?".  Right now one infers it means with other read/write activity on the table - as opposed to, say, additional indexing operations on different connections, which may or may not touch the same tables.  This is the concept of concurrency we want to refer to here - the parameter has already been described above.

David J.

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Michael Paquier
Дата:
Сообщение: Re: BUG #17441: shm_mq receive less data than the sender sends
Следующее
От: Masahiko Sawada
Дата:
Сообщение: Re: BUG #17385: "RESET transaction_isolation" inside serializable transaction causes Assert at the transaction end