Обсуждение: BUG #17446: Suggest updating the section title "Building Indexes Concurrently"
BUG #17446: Suggest updating the section title "Building Indexes Concurrently"
От
PG Bug reporting form
Дата:
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.
Re: BUG #17446: Suggest updating the section title "Building Indexes Concurrently"
От
Michael Paquier
Дата:
On Tue, Mar 22, 2022 at 09:58:28PM +0000, PG Bug reporting form wrote: > 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. FWIW, I don't see the existing section title as really ambigu here, and this wording exists with 10~ years now without anybody complaining about it. REINDEX CONCURRENTLY has been introduced in the last years, and it has influenced this description, but mot by much as the same concepts as CREATE INDEX apply for the building part. -- Michael
Вложения
Re: BUG #17446: Suggest updating the section title "Building Indexes Concurrently"
От
"David G. Johnston"
Дата:
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.