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 1lC3Cp-0005UM-Rf for pgsql-hackers@arkaria.postgresql.org; Tue, 16 Feb 2021 16:28:08 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lC3Cn-00073F-4X for pgsql-hackers@arkaria.postgresql.org; Tue, 16 Feb 2021 16:28:05 +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 1lC3Cm-000738-BA for pgsql-hackers@lists.postgresql.org; Tue, 16 Feb 2021 16:28:04 +0000 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lC3Ce-0002lM-TA for pgsql-hackers@lists.postgresql.org; Tue, 16 Feb 2021 16:28:03 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 4140E5C0110; Tue, 16 Feb 2021 11:27:54 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Tue, 16 Feb 2021 11:27:54 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:subject:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; bh=etd+0uyGQ0b1BhCU7AXnjqANaBgsfjyoIufPAgq1gjQ=; b=VH4DSzD+ 3fbm8eWsLSS7zINBvmU8Ak0cSfZSRb6sYZ/FZl2TVvRoEnXqJEBu7+LNRtHnfGy8 kzaNU/xHSGzJ9CxMQ4e7m/lJHsrF5yf1u0J24yQMSWIo0yG8TKCGrdRo1exGsOSf /2mQj/nx4nwGAJDRxQfPY8wUgvxEmXKwUcfbUyKLh2popaQUYZ89eir+Ikl+qYZM BZ9FjTGdr9xj61O9OKoWDTOX9fXl6EiDh0edxfkR6OWzi9JPkgQ3Hj4sD7GrNTZl MHfNKWnbeJxg4xR35cNFyjeMbI4nceVl/onow8rfhJWOBLioid3bcIR+xaXW9XDB /oO85Nz1kNXYWw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrjedtgdeklecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpeffhffvuffkgggtugfgjggfsehtkeertddtredunecuhfhrohhmpeetlhhvrghr ohcujfgvrhhrvghrrgcuoegrlhhvhhgvrhhrvgesrghlvhhhrdhnohdqihhprdhorhhgqe enucggtffrrghtthgvrhhnpeeufffhjeeiueeuffegvddukeegledtveeivdeiueefieei vefgteehueefteehvdenucfkphepudeltddrleehrdduledrudejjeenucevlhhushhtvg hrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrlhhvhhgvrhhrvgesrghl vhhhrdhnohdqihhprdhorhhg X-ME-Proxy: Received: from perhan.alvh.no-ip.org (unknown [190.95.19.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 4219D108005F; Tue, 16 Feb 2021 11:27:53 -0500 (EST) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 043432A0F29; Tue, 16 Feb 2021 13:27:51 -0300 (-03) Date: Tue, 16 Feb 2021 13:27:50 -0300 From: Alvaro Herrera To: Craig Ringer Cc: Matthieu Garrigues , PostgreSQL-development Subject: Re: PATCH: Batch/pipelining support for libpq Message-ID: <20210216162750.GA13534@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2021-Feb-16, Craig Ringer wrote: > FWIW I'm also thinking of revising the docs to mostly use the term > "pipeline" instead of "batch". Use "pipelining and batching" in the chapter > topic, and mention "batch" in the index, and add a para that explains how > to run batches on top of pipelining, but otherwise use the term "pipeline" > not "batch". Hmm, this is a good point. It means I have a lot of API renaming to do. I'll get on it now and come back with a proposal. -- Álvaro Herrera Valdivia, Chile