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 1lwRoy-00071v-Ab for pgsql-docs@arkaria.postgresql.org; Thu, 24 Jun 2021 16:03:16 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lwRox-0003Pv-B2 for pgsql-docs@arkaria.postgresql.org; Thu, 24 Jun 2021 16:03:15 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lwRox-0003Oc-55 for pgsql-docs@lists.postgresql.org; Thu, 24 Jun 2021 16:03:15 +0000 Received: from mail-pl1-x629.google.com ([2607:f8b0:4864:20::629]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1lwRou-0002j4-Mu for pgsql-docs@lists.postgresql.org; Thu, 24 Jun 2021 16:03:14 +0000 Received: by mail-pl1-x629.google.com with SMTP id y21so3193022plb.4 for ; Thu, 24 Jun 2021 09:03:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=xdNF+ifVeAEGYLZF5Zuw78QpoVAo5gV4F/nRTZhwBUo=; b=FVxIgMURkGGKx+3p26eLbBKwQF7QhNm1MKDdyuwIup7FXEtXShrXBa7ylyI1gzJPz5 kS/vhg0N6IpyOWalxOHgIs+7xLfA3bsMVkjWC6QKzJQ40bJ6onQGRhNa4+LZRTdYI1sH 4nodTD6DwYLoNjaTwN3ANppZ95+sd3OPZ/Vp+qPXWbU1YvJ6L/FhIKscEX93rJ8FcQCV yHTFymTFgKlnOV37gWk143GO/5JcNOBiMthp0qBpfnhJtS5I4Bk4cXhFJ8jIJp7TS8F5 Jhqr5F6NKYcjLhay/Kobh3+FzMQ+wgS0sax9odR5yvY9rpHfIR4KyT9XtiicMPIWEYFQ OFiw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=xdNF+ifVeAEGYLZF5Zuw78QpoVAo5gV4F/nRTZhwBUo=; b=shLNK4e7g4FVHVnlfTSKMNqArMstVGDzPq11fQVwvbAJvveaclpXEmBrC3qNeHHp45 zxodiN+u97z3MHJL4VBAkAIaYSgitdte7Gkrl3zimvtjYLKrUPjcNAIo0uUW3US66Ry2 Tzh7jyQVa10SXeBbEKgU4YeLzhEQNsUjDw49ZSZxK/EhHx5G+fC9yGsjJuncM/XW0T8/ hnovnVO98kjx1fhHLuw/cr5H8n5W6ux+Uk4/rX6/gM+6+gowThIpWzCxfmJhkzjfHi/c +HdX8VUn48/Ya+VsJPoaIQVfMBQYsXBvUXnx3ou6iBPozYMlf3yiRhUhw3NBT+QTxMfH opcg== X-Gm-Message-State: AOAM530TvQeISki1I0aQqdYgihI4s6AOfV7vtaEYpYlg1aNdq/yfw8js nn+m4FPzoyXAmUcdpDb8CykSOWZjtIF1X/SsUPo= X-Google-Smtp-Source: ABdhPJzi1PoS1iUNb7VCB38FtqJFX34hfUrv6NqjMtHey8Ax3SrMlmvagOecAAm5sHHe5iy3qN857IwRDZ5jfyOsnh8= X-Received: by 2002:a17:90b:31cc:: with SMTP id jv12mr6143628pjb.180.1624550591141; Thu, 24 Jun 2021 09:03:11 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: "David G. Johnston" Date: Thu, 24 Jun 2021 09:02:53 -0700 Message-ID: Subject: Re: Has the Update savepoint example outlived its usefulness? To: Peter Eisentraut Cc: Pg Docs Content-Type: multipart/alternative; boundary="000000000000e79a0905c585286e" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000e79a0905c585286e Content-Type: text/plain; charset="UTF-8" On Thu, Jun 24, 2021 at 4:20 AM Peter Eisentraut < peter.eisentraut@enterprisedb.com> wrote: > On 04.06.21 02:08, David G. Johnston wrote: > > The example in the update documentation that does an upsert using a > > savepoint seems like it should just go away now that we have insert...on > > conflict. Making an explicit reference (and link) to that feature in > > the Update documentation should be added in its place (well, under > notes). > > Do we need to replace it by a different example then? > I don't think so. The example that replaces it already exists on the INSERT documentation page, we just need to remove this example on the UPDATE page and point the user there instead. David J. --000000000000e79a0905c585286e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Thu, Jun 24, 2021 at 4:20 AM Peter Eisentraut <peter.eisentraut@enterprise= db.com> wrote:
On 04.06.21 02:08, David G. J= ohnston wrote:
> The example in the update documentation that does an upsert using a > savepoint seems like it should just go away now that we have insert...= on
> conflict.=C2=A0 Making an explicit reference (and link) to that featur= e in
> the Update documentation should be added in its place (well, under not= es).

Do we need to replace it by a different example then?
=
I don't think so.=C2=A0 The example that replaces it alrea= dy exists on the INSERT documentation page, we just need to remove this exa= mple on the UPDATE page and point the user there instead.

David J.
--000000000000e79a0905c585286e--