pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #17446: Suggest updating the section title "Building Indexes Concurrently"
3+ messages / 3 participants
[nested] [flat]
* BUG #17446: Suggest updating the section title "Building Indexes Concurrently"
@ 2022-03-22 21:58 PG Bug reporting form <noreply@postgresql.org>
0 siblings, 2 replies; 3+ messages in thread
From: PG Bug reporting form @ 2022-03-22 21:58 UTC (permalink / raw)
To: pgsql-bugs@lists.postgresql.org; +Cc: troy@frericks.us
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.
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: BUG #17446: Suggest updating the section title "Building Indexes Concurrently"
@ 2022-03-23 04:39 Michael Paquier <michael@paquier.xyz>
parent: PG Bug reporting form <noreply@postgresql.org>
1 sibling, 0 replies; 3+ messages in thread
From: Michael Paquier @ 2022-03-23 04:39 UTC (permalink / raw)
To: troy@frericks.us; pgsql-bugs@lists.postgresql.org
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
Attachments:
signature.asc (application/pgp-signature, 832B) download
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: BUG #17446: Suggest updating the section title "Building Indexes Concurrently"
@ 2022-03-23 05:05 David G. Johnston <david.g.johnston@gmail.com>
parent: PG Bug reporting form <noreply@postgresql.org>
1 sibling, 0 replies; 3+ messages in thread
From: David G. Johnston @ 2022-03-23 05:05 UTC (permalink / raw)
To: troy@frericks.us, PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
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.
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2022-03-23 05:05 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2022-03-22 21:58 BUG #17446: Suggest updating the section title "Building Indexes Concurrently" PG Bug reporting form <noreply@postgresql.org>
2022-03-23 04:39 ` Michael Paquier <michael@paquier.xyz>
2022-03-23 05:05 ` David G. Johnston <david.g.johnston@gmail.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox