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 1oP24w-0005PT-Gv for pgsql-hackers@arkaria.postgresql.org; Fri, 19 Aug 2022 13:30:26 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oP24v-0005G4-Dp for pgsql-hackers@arkaria.postgresql.org; Fri, 19 Aug 2022 13:30:25 +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 1oP24u-0005Ft-Vi for pgsql-hackers@lists.postgresql.org; Fri, 19 Aug 2022 13:30:25 +0000 Received: from mail-il1-x12a.google.com ([2607:f8b0:4864:20::12a]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1oP24r-0003Dw-5S for pgsql-hackers@lists.postgresql.org; Fri, 19 Aug 2022 13:30:23 +0000 Received: by mail-il1-x12a.google.com with SMTP id o14so2306123ilt.2 for ; Fri, 19 Aug 2022 06:30:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20210112.gappssmtp.com; s=20210112; h=user-agent:in-reply-to:content-disposition:mime-version:references :message-id:subject:cc:to:from:date:from:to:cc; bh=sdd3IeT8TW0OYja3f1I+3bTvEJao5snCknUUbNCwI+M=; b=eqGAp4CdeGGQNfdi3jk+Bai0fBMmlThZtIfYqDqfP2nM+KtNB6grCpjfz0Le4uA67V 4aYM/8T3hWTfoxYiBFurzBuVVCio72USnitqADih6r/qYCtZonET1fE1+PakQloO+o56 GvW+wvHa7Lzv9sUcF7L0G2Q1EX5/sK4a8yyi60L/bb4XQP0cuGbdnNU1not53JqoZ+B5 yyUE5RZ9/9E+aW+EqJEyxWp3rO6jjvD9R2HbFE88ROQ0ymSBwM19d1vKb90ZnqfwmRWp GVXQDNW3kDveVwrEgnKbJqRBwXTaWYEl6Q2Czlr7EiPdm9ZrZMEMUANZTezcjY9wFE+F Z73w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=user-agent:in-reply-to:content-disposition:mime-version:references :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc; bh=sdd3IeT8TW0OYja3f1I+3bTvEJao5snCknUUbNCwI+M=; b=lQXXBdmc/jnD/k2ik6X8xEbyF//WxvUNXHK7um+lSQbc/k/AjOk/m5AcYQqWdWKwla Bi1pNg25HyZeTBQ8W+ZwEPT3NND/D1g0ny4OMCoztJ+/to8Uc5+RZ4E72hciQXxVe3e4 lCAs0I3XW30bwr72qYMkkTkRwAx5rFmZTtrkpA08GzZFpKYD6Mk+WnxzIuzzajQSBtjA RrdwiP+9h9LAMsMUkt9l1HncumCLpbFubxb9wVmQtBLs5G2HtMRF8xCO0MkRWKEMtrfH LRiKParQmEcjmMP71D66j+TA1zW3BMlllofQSOPKfLe1YBnzN1DbCDl4NlG2XzEeMKJQ Y91g== X-Gm-Message-State: ACgBeo31fsEka6/IQRI+1qZgUv5o0seoDIzK/CEBLilP1rNep9oTovoz iXeQxYJeqaQ63/DCoDIX2ZkJclSMYjrfYw== X-Google-Smtp-Source: AA6agR7wOTFyHRnd4o5ludVvc/vFiPaF/LZMnKvVj3lV4da5Nm+DA+JPD6dWeAD/hZrOX+0ZXN4W2g== X-Received: by 2002:a05:6e02:1bef:b0:2e5:9ce2:23d0 with SMTP id y15-20020a056e021bef00b002e59ce223d0mr3586113ilv.93.1660915820216; Fri, 19 Aug 2022 06:30:20 -0700 (PDT) Received: from pryzbyj.telsasoft (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id y22-20020a056638229600b0034382439ecasm1758495jas.121.2022.08.19.06.30.17 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 19 Aug 2022 06:30:18 -0700 (PDT) Received: by pryzbyj.telsasoft (Postfix, from userid 1000) id 4A16F80079B; Fri, 19 Aug 2022 08:30:16 -0500 (CDT) Date: Fri, 19 Aug 2022 08:30:16 -0500 From: Justin Pryzby To: Alvaro Herrera Cc: Simon Riggs , "David G. Johnston" , Matthias van de Meent , PostgreSQL Hackers , Peter Eisentraut , Amit Langote , Japin Li , Zhihong Yu , PostgreSQL Developers , Tomas Vondra , Daniel Westermann , Erik Rijkers , Jaime Casanova , Andres Freund Subject: Re: MERGE and parsing with prepared statements Message-ID: <20220819133016.GV26426@telsasoft.com> References: <20220812115325.5b4xuvrqr66wvixp@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220812115325.5b4xuvrqr66wvixp@alvherre.pgsql> User-Agent: Mutt/1.9.4 (2018-02-28) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, Aug 12, 2022 at 01:53:25PM +0200, Alvaro Herrera wrote: > On 2022-Aug-12, Simon Riggs wrote: > > > Sorry, but I disagree with this chunk in the latest commit, > > specifically, changing the MATCHED from after to before the NOT > > MATCHED clause. 3d895bc84 also moved a semicolon into the middle of the sql statement. > > The whole point of the second example was to demonstrate that the > > order of the MATCHED/NOT MATCHED clauses made no difference. > > > > By changing the examples so they are the same, the sentence at line > > 573 now makes no sense. > > Hmm, I thought the point of the example was to show that you can replace > the table in the USING clause with a query that retrieves the column; > but you're right, we lost the thing there. Maybe it was too subtle to > the point that I failed to understand it. Perhaps we can put it back > the way it was and explain these two differences (change of data source > *and* clause ordering) more explicitly. Evidently I misunderstood it, too. -- Justin