[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pgsql-bugs
Subject:    Re: BUG #17446: Suggest updating the section title "Building Indexes Concurrently"
From:       "David G. Johnston" <david.g.johnston () gmail ! com>
Date:       2022-03-23 5:05:13
Message-ID: CAKFQuwaMhJXP1_n_-KfrjvqCJtG_M0NSqMCOxEQQqYhVoQZpoA () mail ! gmail ! com
[Download RAW message or body]

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.

[Attachment #3 (text/html)]

<div dir="ltr"><div dir="ltr"><div class="gmail_default" \
style="font-family:arial,helvetica,sans-serif"><span \
style="font-family:Arial,Helvetica,sans-serif">On Tue, Mar 22, 2022 at 4:19 PM PG Bug \
reporting form &lt;<a \
href="mailto:noreply@postgresql.org">noreply@postgresql.org</a>&gt; \
wrote:</span><br></div></div><div class="gmail_quote"><blockquote class="gmail_quote" \
style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex">The following bug has been logged on the \
website:<br> <br>
Bug reference:         17446<br>
Logged by:               Troy Frericks<br>
Email address:         <a href="mailto:troy@frericks.us" \
target="_blank">troy@frericks.us</a><br> PostgreSQL version: 10.17<br>
Operating system:     Documentation suggestion, ambiguous<br>
Description:            <br>
<br>
<a href="https://www.postgresql.org/docs/9.6/sql-createindex.html#SQL-CREATEINDEX-CONCURRENTLY" \
rel="noreferrer" target="_blank">https://www.postgresql.org/docs/9.6/sql-createindex.html#SQL-CREATEINDEX-CONCURRENTLY</a><br>
 <br>
Suggest changing section title &quot;Building Indexes Concurrently&quot; to \
&quot;Building<br> Indexes Using the CONCURRENTLY Parameter&quot; to eliminate any \
ambiguity.<br></blockquote><div><br></div><div class="gmail_default" \
style="font-family:arial,helvetica,sans-serif">That seems worse.   If anything the \
title should answer the question &quot;Concurrent with What?&quot;.   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.</div><div class="gmail_default" \
style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default" \
style="font-family:arial,helvetica,sans-serif">David J.</div><div \
class="gmail_default" \
style="font-family:arial,helvetica,sans-serif"></div></div></div>



[prev in list] [next in list] [prev in thread] [next in thread]