Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nRjyO-0006t7-2h for pgsql-docs@arkaria.postgresql.org; Wed, 09 Mar 2022 00:14:36 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nRjyL-0002Hd-Qi for pgsql-docs@arkaria.postgresql.org; Wed, 09 Mar 2022 00:14:33 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nRjyL-0002HU-HT for pgsql-docs@lists.postgresql.org; Wed, 09 Mar 2022 00:14:33 +0000 Received: from mail-ot1-x32c.google.com ([2607:f8b0:4864:20::32c]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nRjyI-0004gb-UP for pgsql-docs@lists.postgresql.org; Wed, 09 Mar 2022 00:14:33 +0000 Received: by mail-ot1-x32c.google.com with SMTP id t8-20020a0568301e2800b005b235a56f2dso557789otr.9 for ; Tue, 08 Mar 2022 16:14:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:from:date:message-id:subject:to; bh=t8cNHVFxn9E10WIrG4LuTuFx3LR1a0LomUfNgaJ5FqQ=; b=Fe/szHWoCDlXp32Ipk/qpTaIZwIqr2PP5lkQ64ejLVEUIQIi6Y+mW56o+2NM6zCRRc iiYuWrB5uK39J0Yo7hx615gysw9Q9taWQ93idnJka5uWDuDqqwo1YlKGmoEpLk6YRcfC uFdFQ6BgucaY19zKi2oTribj+iNW+jCtzgfK0hQlJhX0stlE4x2jq34t1Uhw4Kqhbyzl DGvkmW2w7wFndT9OXdBWt5Rm+az9urV+8csUQic/qoxOvCF79IH/dV3A3pbN/Weh+yPP U4FTAgcUMmctpdH4CZdX8tE5F19YxMIbSxP6MYrrP8NkZBuiOu1WcJ5yKcofSaPkdynU qtTg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=t8cNHVFxn9E10WIrG4LuTuFx3LR1a0LomUfNgaJ5FqQ=; b=FsXPtQrsZnoLESSKWbzVR+PGtnOH77FOvzsckU8bzCt/w/L0DRdUWPGTTKgQsM4BOQ 4Sg/5xuoeKsQMRtFXMIP/I64BOk16FOPdWYfVCs5sCUnFsG2v09llq1uKpClQ7kk4wCe 5NxM7B/mP7vPxjjBYC1AId6lrah6Hl+ci6l92uM4zeBQTba0yVlDHc9sSFS9OdGIjUdZ mE+cEFhLXqdyokLWblR0YG3mXj9Pm4eWJ5eHKuy9mUSUpzumadO/PyNxVveasWaEUFOE VHbeGkeO51vhv6bXpYUFIwjhbSe/wW4gHkwUc9sOGbyTzOLcMkDiRg2w358/cwVzmhjp 8dZQ== X-Gm-Message-State: AOAM530++xvVwn36XyJx4jGsFU89BvBm+Y1kPAuQsm2Jj8Vj1wBFSJGx nsRviaP3WGd0dlsYOnhoYapJ27uYGIV1wvs6+EDsLUtMixo= X-Google-Smtp-Source: ABdhPJzYUjDjJ/4gfwXmmZnKqudPZoyXYfNX3apVt40Cb2JVQgQCiEF8n8ToMP3CgxLFMpiNU4bkCSeVDo6GwiUJ3ew= X-Received: by 2002:a9d:64c9:0:b0:5a8:ecae:57b9 with SMTP id n9-20020a9d64c9000000b005a8ecae57b9mr9669350otl.63.1646784868620; Tue, 08 Mar 2022 16:14:28 -0800 (PST) MIME-Version: 1.0 From: "David G. Johnston" Date: Tue, 8 Mar 2022 17:14:11 -0700 Message-ID: Subject: Update wording of INSERT ON CONFLICT "rows proposed for insertion" To: Pg Docs Content-Type: multipart/alternative; boundary="0000000000001d9ccc05d9bdfb69" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000001d9ccc05d9bdfb69 Content-Type: text/plain; charset="UTF-8" Hey, I suggest a minor rewording of: https://www.postgresql.org/docs/devel/sql-insert.html Current: "The SET and WHERE clauses in ON CONFLICT DO UPDATE have access to the existing row using the table's name (or an alias), and to [rows] proposed for insertion using the special excluded table." Becomes: "The SET and WHERE clauses in ON CONFLICT DO UPDATE have access to the existing row using the table's name (or an alias), and to [the corresponding row] proposed for insertion using the special excluded table." The plural "rows" just reads oddly since in any single evaluation only one row is going to be present in the excluded table for the "existing row" in the target table. David J. --0000000000001d9ccc05d9bdfb69 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hey,

I suggest a minor rewording o= f:

https://www.postgresql.org/docs/devel/sql-insert.html

Current:
"The SET and WHERE clauses in = ON CONFLICT DO UPDATE have access to the existing row using the table's= name (or an alias), and to [rows] proposed for insertion using the special= excluded table."

Becomes:
"The = SET and WHERE clauses in ON CONFLICT DO UPDATE have access to the existing = row using the table's name (or an alias), and to [the corresponding row= ] proposed for insertion using the special excluded table."
<= div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif= ">
The plural "rows" just reads oddly since in any si= ngle evaluation only one row is going to be present in the excluded table f= or the "existing row" in the target table.

D= avid J.

--0000000000001d9ccc05d9bdfb69--