Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gOsmy-0003n1-Ur for pgsql-docs@arkaria.postgresql.org; Mon, 19 Nov 2018 23:17:09 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gOsmw-0006l7-9w for pgsql-docs@arkaria.postgresql.org; Mon, 19 Nov 2018 23:17:06 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gOsmw-0006l0-49 for pgsql-docs@lists.postgresql.org; Mon, 19 Nov 2018 23:17:06 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gOsms-00084j-SI for pgsql-docs@lists.postgresql.org; Mon, 19 Nov 2018 23:17:05 +0000 Received: from bruce by momjian.us with local (Exim 4.84_2) (envelope-from ) id 1gOsmq-0000Rg-KY; Mon, 19 Nov 2018 18:17:00 -0500 Date: Mon, 19 Nov 2018 18:17:00 -0500 From: Bruce Momjian To: antonie@quantsolutions.co.za, pgsql-docs@lists.postgresql.org Subject: Re: INSERT INTO RETURNING SYNTAX ERROR Message-ID: <20181119231700.GG28656@momjian.us> References: <154019774706.30914.7566737339920091737@wrigleys.postgresql.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <154019774706.30914.7566737339920091737@wrigleys.postgresql.org> User-Agent: Mutt/1.5.23 (2014-03-12) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Mon, Oct 22, 2018 at 08:42:27AM +0000, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/9.6/static/sql-insert.html > Description: > > When using the RETURNING extension on the INSERT function when nested, does > not propagate the return value up, and causes a syntax error on the "INTO" > keyword, this is because the RETURNING extension is also expecting in "INTO" > key word, which isn't mentioned anywhere in the documentation? Uh, can you show us an example of the failure? -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription +