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 1ptwmU-0005DL-9p for pgsql-bugs@arkaria.postgresql.org; Tue, 02 May 2023 20:39: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 1ptwmS-0001t5-Vt for pgsql-bugs@arkaria.postgresql.org; Tue, 02 May 2023 20:39:24 +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 1ptwmS-0001sw-NX for pgsql-bugs@lists.postgresql.org; Tue, 02 May 2023 20:39:24 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1ptwmM-000DKi-0x for pgsql-bugs@lists.postgresql.org; Tue, 02 May 2023 20:39:24 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 342KdFPe2830146; Tue, 2 May 2023 16:39:15 -0400 From: Tom Lane To: Daniel Gustafsson cc: Kieran McCusker , pgsql-bugs@lists.postgresql.org Subject: Re: plpython does not honour max-rows In-reply-to: References: <711512C7-2BC2-4901-A368-6A5A23023F72@yesql.se> <2678018.1683036150@sss.pgh.pa.us> Comments: In-reply-to Daniel Gustafsson message dated "Tue, 02 May 2023 22:34:04 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2830144.1683059955.1@sss.pgh.pa.us> Date: Tue, 02 May 2023 16:39:15 -0400 Message-ID: <2830145.1683059955@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Daniel Gustafsson writes: >> On 2 May 2023, at 16:02, Tom Lane wrote: >> I wonder whether the similar plperl and pltcl wrappers are also >> documentation-shy here. > It seems like they are all a bit thin on explaining this. The attached diff > copies the wording (which unsurprisingly is pretty good IMO) into the > plperl/python/tcl documentation. Ah, seems like we set to work on this at the same time :-( I thought that s/max-rows/limit/ would be a good idea, mainly because plperl's spi_exec_prepared uses that name as a caller-exposed hash key. I'm not especially concerned about the wording otherwise. regards, tom lane