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 1nWGtW-0008De-MR for pgsql-docs@arkaria.postgresql.org; Mon, 21 Mar 2022 12:12:18 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nWGtV-0000I4-H6 for pgsql-docs@arkaria.postgresql.org; Mon, 21 Mar 2022 12:12:17 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nWGtV-0000Hn-9U for pgsql-docs@lists.postgresql.org; Mon, 21 Mar 2022 12:12:17 +0000 Received: from mail-pf1-x42f.google.com ([2607:f8b0:4864:20::42f]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nWGtS-0006NX-TY for pgsql-docs@lists.postgresql.org; Mon, 21 Mar 2022 12:12:16 +0000 Received: by mail-pf1-x42f.google.com with SMTP id g19so15224338pfc.9 for ; Mon, 21 Mar 2022 05:12:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=date:from:to:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=T7qH/UNFn1+kr0tr4u68KjYztgC+fgWqiDDyUinxSks=; b=DbXx6Mc2mgWbKgYKyoR5i+zB4J4zeX15lE2nADwt//NmeSRstOnO/YP/VYQwhBG0Fe FUtdnod89GBpM9zXBev9paCz///0yJf+E9iAmBqQioHq01blNbJRcDX+0HP04kLW7Bdb ZYPFnLXfKefHYc3UNmOEpEyeiHXuDXsSdUabZojpFc1sumeAhzvzOn3kBT3mEFN/WONR HtqOSDP2XiTWwDXHFmN81MUYHZXs1YBboC3eEuss30Gbof+NhCfDF8kKnBMQFtL7eyxx S70YQe/LXwkdVEfX+El++tKZulgK8CL1qvY8pT/981Ti6Dq2uvBktIFeyvqg+E/sD7uQ skfA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=T7qH/UNFn1+kr0tr4u68KjYztgC+fgWqiDDyUinxSks=; b=sh0QfuDvjGpv6KtTC2eYb68KhMfCXHsu4qXpRNlP6L5e33qXkVDJc9GN1ZLthY9DDd tsG0L7C2IgwiVm0WcFfRh6x+fg3a8gGrJflAnoVRQVJU6BvwIQdEGvv5F6cVLZMdLmC6 gxoZ+arQfWJ6ygUGWLAEXzstF5ayRm1ThVp5y0Edc3hWlRy/IvWbB52VuCcQdRWhmj4h mxIVNUy0baXFWa7wiQLkFiawdWHhxIQJigcpUyHEeXifR6befhYVPH+jMQWbGL3QKdcI GqnujQWi2Rnx0K6KObZBi06M7rA1k15ckY0CsI/pVtP5E6AEkuwOGHsTQusmEv6fwzLO SRXw== X-Gm-Message-State: AOAM530gJdLFh0rf09GzlkSGgiBY5JNpQl0zDeaDh9pyX4651QgcBo3r REAtbOaaqd/aTYwyuVKQixo= X-Google-Smtp-Source: ABdhPJzYl2696s2/40HthCfe4PxOIW4Wl/tEOGt2QsucFmH9S7ljU6oxsp9aNeG3bc8sv0zlMQlg3Q== X-Received: by 2002:a62:1715:0:b0:4fa:7a4f:e64c with SMTP id 21-20020a621715000000b004fa7a4fe64cmr14204689pfx.32.1647864732771; Mon, 21 Mar 2022 05:12:12 -0700 (PDT) Received: from jrouhaud (2001-b011-1005-bfdd-7539-0b5a-e8e9-5a84.dynamic-ip6.hinet.net. [2001:b011:1005:bfdd:7539:b5a:e8e9:5a84]) by smtp.gmail.com with ESMTPSA id j6-20020a63b606000000b003808b0ea96fsm13984258pgf.66.2022.03.21.05.12.11 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 21 Mar 2022 05:12:12 -0700 (PDT) Date: Mon, 21 Mar 2022 20:12:10 +0800 From: Julien Rouhaud To: miguelgilmartinez@gmail.com, pgsql-docs@lists.postgresql.org Subject: Re: SQL "RETURNING * | output_expression [ [ AS ]" is wrong Message-ID: <20220321121210.pknnj3d4k54ddprw@jrouhaud> References: <164785739575.668.4514247042951418611@wrigleys.postgresql.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <164785739575.668.4514247042951418611@wrigleys.postgresql.org> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, On Mon, Mar 21, 2022 at 10:09:55AM +0000, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Hi! AFAIK, UPDATE .... RETURNING works with INTO varname, not AS I think you're confusing with plpgsql's INTO [1]. The documented syntax works as expected: # UPDATE tt SET id = 2 WHERE id = 1 RETURNING id AS new_id; new_id -------- 2 (1 row) [1] https://www.postgresql.org/docs/current/plpgsql-statements.html#PLPGSQL-STATEMENTS-SQL-ONEROW