Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t8LHi-003aAV-7f for pgsql-hackers@arkaria.postgresql.org; Tue, 05 Nov 2024 15:15:57 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1t8LHf-00Ej1P-DY for pgsql-hackers@arkaria.postgresql.org; Tue, 05 Nov 2024 15:15:55 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t8LHf-00EizI-3Q for pgsql-hackers@lists.postgresql.org; Tue, 05 Nov 2024 15:15:55 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t8LHc-000L69-1B for pgsql-hackers@lists.postgresql.org; Tue, 05 Nov 2024 15:15:55 +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 4A5FFmEv3051356; Tue, 5 Nov 2024 10:15:48 -0500 From: Tom Lane To: Robert Haas cc: Gurjeet Singh , "Ryohei Takahashi (Fujitsu)" , "pgsql-hackers@lists.postgresql.org" Subject: Re: doc: pgevent.dll location In-reply-to: References: Comments: In-reply-to Robert Haas message dated "Tue, 05 Nov 2024 10:09:54 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <3051354.1730819748.1@sss.pgh.pa.us> Content-Transfer-Encoding: 8bit Date: Tue, 05 Nov 2024 10:15:48 -0500 Message-ID: <3051355.1730819748@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Robert Haas writes: > On Tue, Nov 5, 2024 at 1:00 AM Gurjeet Singh wrote: >> I'm unable to confirm the veracity of the claim that the pgevent.dll >> file on Windows is now placed in a different directory, and that this >> is a result of meson builds. But the patch looks good to me; it >> applies cleanly to REL_17_STABLE and main branches. > I think we will need to find someone who can confirm whether or not > the claim is correct. More to the point: if that does happen, isn't it a bug to be fixed rather than documented? regards, tom lane