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 1loxOt-0003FM-Fb for pgsql-docs@arkaria.postgresql.org; Fri, 04 Jun 2021 00:09:23 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1loxOs-0004mW-5Y for pgsql-docs@arkaria.postgresql.org; Fri, 04 Jun 2021 00:09:22 +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 1loxOr-0004mO-TQ for pgsql-docs@lists.postgresql.org; Fri, 04 Jun 2021 00:09:21 +0000 Received: from mail-pl1-x62c.google.com ([2607:f8b0:4864:20::62c]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1loxOl-0000Zu-GJ for pgsql-docs@lists.postgresql.org; Fri, 04 Jun 2021 00:09:20 +0000 Received: by mail-pl1-x62c.google.com with SMTP id v13so3735829ple.9 for ; Thu, 03 Jun 2021 17:09:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=fM/I3luQMJkdJ18ULXD6NepZd+n3FCxJjeL2yzSjpIg=; b=I8FbTQpGJWBuVu5mj8NQm+oRRLmx4LhcbVQRyDLK19ZTBT4JT+rn3qDn011UiFNTvi 89jJ3NWgREYHIBGN9xHrclmWc/ZJJFk2PDXAW6SrwfutAjYV4jV/ZFMafk2ubBKZANwa 9iVAwRs6PAayyuRD9vN3HRCckR9Ff9I9h3d+QUgpPsvo5zed5tlND3+UvYnF1NNwZFlR SOFMDzgTO2wqSitgJXZi/axXAl+JTVuNHPOBE/FOCB4DIVBJJX0Y7HTgvGqyOfiOp9qB TfYYxZd6sbMu9jX8zYejGoe7WLTNfc2nbS92RwQA0/EhJ3GR9IGcKtUu4EwRVrKLKnMu yUJA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=fM/I3luQMJkdJ18ULXD6NepZd+n3FCxJjeL2yzSjpIg=; b=dN7e16YTidd4GYJ25rMN+GsUotfj9FNS+G3KTkkR5I/oHCCPIWLUhO/VmdnRWa4Igu 7gN7qSVHhkE/zaylqJXbF5NCGljr/BFGyOXjWAhtThLEMBXt0A2yk3N78Hdeig8NK5e/ B3h7IjcRdzX2Co51/BdTexoLZmU9TTcPNZ1uxz40tvLAGZsOfglGMXg1uNe0sI2F9yGd FDAGMTC3ksh5vkWDOH6V7AjfkBn0B5CTJCwLezMWLG99RNKPP2Nnf/32a4D/+vyX+H1w 3uVTQPsfyEaSM8HyhnyodBGbwk6FBdFMz6bbuGk0vn/gGD8yl/I+WdGjP7FfqTmgU091 hYaw== X-Gm-Message-State: AOAM5326gz4CISeMOfBZ0Caqwv7NCvwVXvfnEmSpAPMb2ZbbYEHUSbF0 stQgycuGNQCgVdhl4OGnpwcdaX9MJqaPN6xpE4wyOGbeQyo= X-Google-Smtp-Source: ABdhPJzaVrzetLeVmacMviG2IjmsMydrTg1OsrckDOEEMI+sSrgI9LlFCO1TJNKzqbIBkRLWx6Qd8sb2+r9Wc+xbiig= X-Received: by 2002:a17:90b:3001:: with SMTP id hg1mr13681174pjb.169.1622765353806; Thu, 03 Jun 2021 17:09:13 -0700 (PDT) MIME-Version: 1.0 From: "David G. Johnston" Date: Thu, 3 Jun 2021 17:08:55 -0700 Message-ID: Subject: Has the Update savepoint example outlived its usefulness? To: Pg Docs Content-Type: multipart/alternative; boundary="00000000000077af4705c3e5808a" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000077af4705c3e5808a Content-Type: text/plain; charset="UTF-8" Hey, 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). David J. --00000000000077af4705c3e5808a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hey,

The example in the update doc= umentation 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 ref= erence (and link) to that feature in the Update documentation should be add= ed in its place (well, under notes).

David J.
=
--00000000000077af4705c3e5808a--