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 <pgsql-docs-owner+archive@lists.postgresql.org>)
	id 1kb298-0001Xi-4A
	for pgsql-docs@arkaria.postgresql.org; Fri, 06 Nov 2020 13:51:18 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-docs-owner+archive@lists.postgresql.org>)
	id 1kb294-0006gG-SS
	for pgsql-docs@arkaria.postgresql.org; Fri, 06 Nov 2020 13:51:14 +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 <jkatz@postgresql.org>)
	id 1kb294-0006g9-MM
	for pgsql-docs@lists.postgresql.org; Fri, 06 Nov 2020 13:51:14 +0000
Received: from meldrar.postgresql.org ([2a02:c0:301:0:ffff::31])
	by magus.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <jkatz@postgresql.org>)
	id 1kb28x-0001QW-Ic
	for pgsql-docs@lists.postgresql.org; Fri, 06 Nov 2020 13:51:14 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
	d=postgresql.org; s=20171124; h=Content-Transfer-Encoding:Content-Type:
	In-Reply-To:MIME-Version:Date:Message-ID:From:References:Cc:To:Subject:Sender
	:Reply-To:Content-ID:Content-Description;
	bh=fEvh5rR+J0ndXXQmuG8ETAT/k7k29QUgyiR/EAgoVvA=; b=Rx3+P9TWf8fXxP31ZJpN08qW2v
	JiAsEKz8xgkD1CQSambbwwakqIJ2aWz5Ts3jCJpHvdijOOKfuHZo0ba8pVRHcnJ1OnBsF/RViR6Kn
	WQyrIwMUGloZ5i3SqZw5ZVAENfJH6qXqZoF8gDlzowJktJZ2blInnZNDEm+loxV18T1fCrSZlKbGN
	eDrZgiKfxB7HHTpFDJ2vCe9cJy9qgqMh2nEigvbBd8rHHA1kcKETdqo2Z7uSG72JeaptH5H2P05VP
	h53Gx/7vZwCiMsxU/WVUiPrb22G2LA4RizW0YPTRh4EQfa0ZXTq58tf0v6+gVm3Tx39hqTdDwErcq
	1/mtHj8w==;
Received: from pool-173-56-10-231.nycmny.fios.verizon.net ([173.56.10.231]
 helo=Ph33rHippo.home)
	by meldrar.postgresql.org with esmtpsa
 (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128)
	(Exim 4.92)
	(envelope-from <jkatz@postgresql.org>)
	id 1kb28q-00081J-JS; Fri, 06 Nov 2020 13:51:04 +0000
Subject: Re: Possible Example Error in Documentation
To: Tom Lane <tgl@sss.pgh.pa.us>, noogrub@gmail.com
Cc: pgsql-docs@lists.postgresql.org
References: <160460554398.25505.16500236866893587292@wrigleys.postgresql.org>
 <1532072.1604623075@sss.pgh.pa.us>
From: "Jonathan S. Katz" <jkatz@postgresql.org>
Message-ID: <1d0dc7ec-69d6-1f5e-8540-9a5e85f74d59@postgresql.org>
Date: Fri, 6 Nov 2020 08:50:57 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0)
 Gecko/20100101 Thunderbird/78.4.0
MIME-Version: 1.0
In-Reply-To: <1532072.1604623075@sss.pgh.pa.us>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
List-Id: <pgsql-docs.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-docs@lists.postgresql.org>
List-Owner: <mailto:pgsql-docs-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-docs>
Precedence: bulk

On 11/5/20 7:37 PM, Tom Lane wrote:
> PG Doc comments form <noreply@postgresql.org> writes:
>> The following documentation comment has been logged on the website:
>> Page: https://www.postgresql.org/docs/12/plpgsql-transactions.html
>> Description:
> 
>> We are using Postgres 12. When I use the example given for
>> transaction_test1() from the documentation here:
>> https://www.postgresql.org/account/comments/new/12/plpgsql-transactions.html/,
>> the procedure is created without incident.  However, when I attempt "CALL
>> transaction_test1();", I receive the "invalid transaction termination"
>> error.
> 
> Hmm, it works for me.

Ditto.

I did get that error message if I put a "BEGIN;" statement before
executing the CALL statement.

Jonathan