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 1pUqRR-0001bX-FJ for pgsql-hackers@arkaria.postgresql.org; Wed, 22 Feb 2023 14:49:57 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pUqRQ-0005dK-9m for pgsql-hackers@arkaria.postgresql.org; Wed, 22 Feb 2023 14:49:56 +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 1pUqRQ-0005dB-0F for pgsql-hackers@lists.postgresql.org; Wed, 22 Feb 2023 14:49:56 +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 1pUqRN-0003zH-4F for pgsql-hackers@postgresql.org; Wed, 22 Feb 2023 14:49:55 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id BAE825C0144; Wed, 22 Feb 2023 09:49:50 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Wed, 22 Feb 2023 09:49:50 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:reply-to:sender :subject:subject:to:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; t=1677077390; x=1677163790; bh=r Ndl0nS8O4ZXrtx0pJq8meIkxya7OWnTH42WDyERh+U=; b=MWHcPEcnQ86wGeESL /HFRRsL48/eDUM5+AcFWGr8dTjSfV41urG2/7Mqqdvc0ahZTKHOzPAM4eftUkncT MEZin5XV51SP4WBESpcUw7bjWNmT1WE2EHvnpCCdQfg3D5byiz0X9Cy68qKUPTX4 D5BoWhI09mUJV+8d8+qTstIU7Ni9nfOKaO1XR+u0CO6lm/n696bVdw4sduIOKEyk O0N+BL7gqPlGjdJ/HE6eQbWJXpZTJh0zEfQFcy54fjFvn/jDveU+SZEZegNE9pjd So1366Cg9CAN7CkP75Xcd2xtmqV/gw4cObrcW9Y1HVDDYQV6iEIgjFdf4YZranZP xQXnA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrudejledgieekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvfevuffkgggtugfgjgesthekredttddtjeenucfhrhhomheptehlvhgr rhhoucfjvghrrhgvrhgruceorghlvhhhvghrrhgvsegrlhhvhhdrnhhoqdhiphdrohhrgh eqnecuggftrfgrthhtvghrnhepvdektdffudfftdffffehfffhjeejhffgieeuueekjeek fffgudffhfduffffueevnecuffhomhgrihhnpegvnhhtvghrphhrihhsvggusgdrtghomh enucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrlhhv hhgvrhhrvgesrghlvhhhrdhnohdqihhprdhorhhg X-ME-Proxy: Feedback-ID: ia2694551:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 22 Feb 2023 09:49:50 -0500 (EST) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id B0CDC9C; Wed, 22 Feb 2023 15:49:48 +0100 (CET) Date: Wed, 22 Feb 2023 15:49:48 +0100 From: Alvaro Herrera To: Peter Eisentraut Cc: pgsql-hackers Subject: Re: pgindent vs. git whitespace check Message-ID: <20230222144948.svf2szymuqbjfebs@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <480e3c67-b703-46ff-a418-d3b481d68372@enterprisedb.com> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2023-Feb-22, Peter Eisentraut wrote: > In the meantime, I suggest we work around this, perhaps by > > conn = libpqsrv_connect_params(keywords, values, /* expand_dbname = */ false, > PG_WAIT_EXTENSION); I suggest conn = libpqsrv_connect_params(keywords, values, false, /* expand_dbname */ PG_WAIT_EXTENSION); which is what we typically do elsewhere and doesn't go overlength. -- Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/ Maybe there's lots of data loss but the records of data loss are also lost. (Lincoln Yeoh)