Re: Upsert error "column reference is ambiguous" - Mailing list pgsql-general

From David G. Johnston
Subject Re: Upsert error "column reference is ambiguous"
Date
Msg-id CAKFQuwZzU9D6vuPbWoQM7tGS8EuSoGGCUuFGJuJrhFzmCsjqUg@mail.gmail.com
Whole thread Raw
In response to Upsert error "column reference is ambiguous"  (Tim Starling <tstarling@wikimedia.org>)
List pgsql-general
On Sunday, April 27, 2025, Tim Starling <tstarling@wikimedia.org> wrote:
thus allowing it to DWIM.

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

Personally I’d be fine with the reduced helpfulness in trying to prevent 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.

pgsql-general by date:

Previous
From: Tim Starling
Date:
Subject: Upsert error "column reference is ambiguous"
Next
From: KK CHN
Date:
Subject: pgbackrest with two remote backend servers fails