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 1t8LSk-003cIr-P4 for pgsql-hackers@arkaria.postgresql.org; Tue, 05 Nov 2024 15:27:22 +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 1t8LSh-00EwJb-Ox for pgsql-hackers@arkaria.postgresql.org; Tue, 05 Nov 2024 15:27:20 +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 1t8LSh-00EwJT-FK for pgsql-hackers@lists.postgresql.org; Tue, 05 Nov 2024 15:27:20 +0000 Received: from mail-lj1-x22a.google.com ([2a00:1450:4864:20::22a]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1t8LSd-000LCw-Fs for pgsql-hackers@lists.postgresql.org; Tue, 05 Nov 2024 15:27:19 +0000 Received: by mail-lj1-x22a.google.com with SMTP id 38308e7fff4ca-2fb51f39394so46792601fa.2 for ; Tue, 05 Nov 2024 07:27:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pgadmin.org; s=google; t=1730820434; x=1731425234; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=aWTq6bAY901LU4/G2JhWur4/wFf2QlmMRnOVOQ9qjMs=; b=gmpe+LT3z89p6fEoL6H91h5V+Ac+1TAjavEZ+fODZfO9gKnm2pVfB3f5q+LbjrnjXg TgYvgkEYJB/8dAFVCXEZAs52Xs9heHevSmsn/jMvjBNuOVbjF+6Ldmk8iyrvnQtuTseG 8J87enNKsg3kn7+reFQ4FS2yKrmcL7twdnb2IgLldf/rG2C+J/Oa8KbHulbNKBz0xM8c ojyX6orMRm0O9COFVXMqmG5LTVoiClN/Uwil/KP/M1i8JB3bcRjQQUKv3D+NBX6YG1Mi sYCVAO/nnztWEpiIKPqq1pDb32CZBVkjVI8xXGV0nSkpGMOzXsax8nP7SHjVfE2BoXZX kYmQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1730820435; x=1731425235; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=aWTq6bAY901LU4/G2JhWur4/wFf2QlmMRnOVOQ9qjMs=; b=Wva8JiNO7B47JEPspJySAF60l7UT+tWHUjbwb/mpTmdHBqouDI/0kzPA/JlIDaNIB9 yQTGNigYgA0Slg1r3qaX9XdlzFU0Zup3XYZV4veGkVqwdBWT+3kxTwT7UYbhRT6xKuj+ zRS8ElfRRVNK7+zsyZG8hX2MaVpNpcdd4kyngPurd0IOIJNA7U04ERxRLHKJ/AArX4IC qL+QfoVb0eIF6aTWFb4vCh3LNjVrDU1OjiV1BEv97qGiMRuFsPwoUasRiNe0eauYFsd/ QqP8KBaptQxqzZpVW5Yy2k7/kdT3LgvHmLfI2rk819yuLPtFOgq+c3jgpQsM3AEoh4Uo V9NA== X-Forwarded-Encrypted: i=1; AJvYcCVjYoT781vmF8T07+zNjl4WYJOJRgZ4tLnJGjiPoGVIT9XSD201WRjjZ0+0iIbnFFNIEvMWi++aOgP456By@lists.postgresql.org X-Gm-Message-State: AOJu0YxOHumcbmGo0tLXrU0ewUr4bCiLA6SuUIbxIk3tHt76qHYhQYyt S+3y1GL+c34u3fZOrJQbKV+fVyJVKYwncAQdeXFtfD5Xqu31VbqkmIs99ZnIAnZPnjggdfuFRAc QJ5DEVmwcrsMDdUcKfMF++0JK5svY+Zq+mkgF X-Google-Smtp-Source: AGHT+IGz+etkFj3nrTrcZ0mAJLLqDwFTlzalLAlt33KHLuKgDEkIl4N5lWqR6XcSSOpt97nNc/pAE8wtGkh39eqKSP0= X-Received: by 2002:a05:651c:4ca:b0:2fa:cc86:f217 with SMTP id 38308e7fff4ca-2fcc940c73cmr173794321fa.35.1730820434245; Tue, 05 Nov 2024 07:27:14 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Dave Page Date: Tue, 5 Nov 2024 15:27:03 +0000 Message-ID: Subject: Re: doc: pgevent.dll location To: Robert Haas Cc: Gurjeet Singh , "Ryohei Takahashi (Fujitsu)" , "pgsql-hackers@lists.postgresql.org" Content-Type: multipart/alternative; boundary="000000000000275c8a06262c09c1" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000275c8a06262c09c1 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, 5 Nov 2024 at 15:10, Robert Haas wrote: > On Tue, Nov 5, 2024 at 1:00=E2=80=AFAM Gurjeet Singh w= rote: > > 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. > It is correct. In v16, it was in lib/, in v17, bin/. However, on Windows I think it probably makes (marginally) more sense to include it in bin/ - we already have other libraries in there that are linked at compile time. pgevent is something of a special case, but it's probably more similar to those libraries than the extensions etc. that are in lib/. Related sidenote: I got a complaint today that pg_regress.exe is no longer part of the Windows installation footprint - and indeed, it's not installed at all with Meson builds, which is problematic for those doing CI/CD testing of extensions. --=20 Dave Page pgAdmin: https://www.pgadmin.org PostgreSQL: https://www.postgresql.org --000000000000275c8a06262c09c1 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Tue, 5 Nov 2024 at 15:10, Robert H= aas <robertmhaas@gmail.com&= gt; wrote:
On Tue, Nov 5, 2024 at 1:00=E2=80=AFAM= Gurjeet Singh <gu= rjeet@singh.im> wrote:
> I'm unable to confirm the veracity of the claim that the pgevent.d= ll
> file on Windows is now placed in a different directory, and that this<= br> > 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.

It is correct. In= v16, it was in lib/, in v17, bin/.

However, on Wi= ndows I think it probably makes (marginally) more sense to include it in bi= n/ - we already have other libraries in there that are linked at compile ti= me. pgevent is something of a special case, but it's probably more simi= lar to those libraries than the extensions etc. that are in lib/.

Related sidenote: I got a complaint=C2=A0today that pg_regr= ess.exe is no longer part of the Windows installation footprint - and indee= d, it's not installed at all with Meson builds, which is problematic fo= r those doing CI/CD testing of extensions.
=C2=A0
--
--000000000000275c8a06262c09c1--