Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1u9Hm7-00064v-NP for pgsql-general@arkaria.postgresql.org; Mon, 28 Apr 2025 06:15:32 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1u9Hm3-00CA7w-Rh for pgsql-general@arkaria.postgresql.org; Mon, 28 Apr 2025 06:15:28 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1u9Hm3-00CA7o-GL for pgsql-general@lists.postgresql.org; Mon, 28 Apr 2025 06:15:28 +0000 Received: from mail-oo1-xc2a.google.com ([2607:f8b0:4864:20::c2a]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1u9Hm1-002RWJ-17 for pgsql-general@lists.postgresql.org; Mon, 28 Apr 2025 06:15:27 +0000 Received: by mail-oo1-xc2a.google.com with SMTP id 006d021491bc7-6066c02cd92so511146eaf.2 for ; Sun, 27 Apr 2025 23:15:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1745820924; x=1746425724; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=/38PkaE8mjS1rRwFEoFDbd1jL7IISu5R7zVTN7RH3lo=; b=Ab9n1PeXqdqF3P0vPyrIRoctCHxry3ewX+P4vNkVWGY+dcYaFBG/FUIDhCSmYznnFP iak4o3nHDj9rZbfgWRWyiXJvkyBSW5VUcBtH+oZCKqFiA6YmRQxmWcRPQIp6HhDRXUKu EF2tbqFkWTDVo3zev/J8EjMucnfV9AQMfTQPvNMjl3nAqoZ7LSCjkcjGO7ZDcR09xoSN ZDYz7mAAnxZ+WNx5yn0bFOvQ6wFSi6gFhZFiTDdTaDX8qoV/pCIqInv/5dLPCCkOXLNV YE9vjFbHujrptN6BLgGhvgXgR4ZXXt59QKn74YiJ5EDVOiWwxIY98a/OVB02pm0iwYZ3 9H7Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1745820924; x=1746425724; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=/38PkaE8mjS1rRwFEoFDbd1jL7IISu5R7zVTN7RH3lo=; b=SzbkprWEL//OGxYd7hEZASootbX+RflDyEaDcLwn1uzbvMWWemfuUsDPjAFfDP9SMF MnIxAfEIaroNpngZHThrF0Q9OV5d0zjfDnYjVgfAjpSUy9cxclclPxMXkEPj+oJ7B9Xn c2LV+0tjwTLBpWpG6JSOljRLotocbtDMNhRvtBPZxrSeN91teAitz4diColRS8JVhxZK ZPXtVCeUiKGPDUvG+tnoOV7dCAQcyhmZIWdhzO/1qQdhrUAuA6TuTL7AOKSIDlpuf1M/ HvOs13O3Ir7g40km2RSEaH16feKN70JDmJc7FcnR3ioU5prLlP0tYXG46CQlcvwN2C7N atEg== X-Gm-Message-State: AOJu0YylHrDzZM1pHv34MXseKN28yqXFtG9AY3NjukIyrbxTPY7ULUHo L9Zjk47ghTjRi7dEke9FSeVGHoVDG7a8yCcFV7ucSAk/p5Jlcky8pSGunZSA7hbERc8wkhfLNiC 3f5Fek4MUdHl8+Y8J5lrHHlpqD0A= X-Gm-Gg: ASbGncs7UPCNnRYUKH6Uq/xvp15Nq3JOHsThwPlYXV83uh2ODyhsIzCjyVVxKrW+25b oN/I2hfoJVz4MjMq2gfC5cSUPI8mgLZa0GJAWtEkKVMr39L2VkgTCt+dzjlxmpb8N9mPV+wg8i8 NEw85TD66RXULThslYDtlJ X-Google-Smtp-Source: AGHT+IHt6OobQjf3ofK5sLaReOcklw5Tv+1Zh5xBgRToGTw/CmRlflckxqHqEjDuTIfRRCL7h7kiVEHxJ9LKMPHRlOI= X-Received: by 2002:a05:6870:4595:b0:2d6:bc4:e4e4 with SMTP id 586e51a60fabf-2d99d75619dmr6286211fac.4.1745820924381; Sun, 27 Apr 2025 23:15:24 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a05:6802:1e0e:b0:589:13f9:e937 with HTTP; Sun, 27 Apr 2025 23:15:23 -0700 (PDT) In-Reply-To: References: From: "David G. Johnston" Date: Sun, 27 Apr 2025 23:15:23 -0700 X-Gm-Features: ATxdqUGjYzjfbjqzRKNN8ZvTMqbedwZxBYraOsJl850JVbRhgn8Hqy4POxVHes8 Message-ID: Subject: Re: Upsert error "column reference is ambiguous" To: Tim Starling Cc: "pgsql-general@lists.postgresql.org" Content-Type: multipart/alternative; boundary="0000000000000a0cc20633d09cae" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000000a0cc20633d09cae Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sunday, April 27, 2025, Tim Starling wrote: > thus allowing it to DWIM. We intentionally choose (or, in any case have established) a SWYM approach here. Personally I=E2=80=99d be fine with the reduced helpfulness in trying to pr= event buggy queries in the interest of being more conforming with the broader world. I am curious as to whether we are in strict adherence to the SQL Standard on this point though. Makes deviation a bit tougher to justify. It does seem that project policies would prevent back-patching such a change. David J. --0000000000000a0cc20633d09cae Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sunday, April 27, 2025, Tim Starling <tstarling@wikimedia.org> wrote:
thus allowing it to DWIM.

We inte= ntionally choose (or, in any case have established) a SWYM approach here.

Personally I=E2=80=99d be fine with the reduced hel= pfulness in trying to prevent buggy queries in the interest of being more c= onforming with the broader world.=C2=A0 I am curious as to whether we are i= n strict adherence to the SQL Standard on this point though.=C2=A0 Makes de= viation a bit tougher to justify.

It does seem tha= t project policies would prevent back-patching such a change.
David J.

--0000000000000a0cc20633d09cae--