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 1sHpx5-00B7Ql-Hg for pgsql-hackers@arkaria.postgresql.org; Thu, 13 Jun 2024 19:17:39 +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 1sHpx3-0061pM-DF for pgsql-hackers@arkaria.postgresql.org; Thu, 13 Jun 2024 19:17:38 +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 1sHpx3-0061pD-1i for pgsql-hackers@lists.postgresql.org; Thu, 13 Jun 2024 19:17:37 +0000 Received: from mail-lj1-x22f.google.com ([2a00:1450:4864:20::22f]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sHpx0-001Vr8-1p for pgsql-hackers@postgresql.org; Thu, 13 Jun 2024 19:17:37 +0000 Received: by mail-lj1-x22f.google.com with SMTP id 38308e7fff4ca-2ebec2f11b7so13788731fa.2 for ; Thu, 13 Jun 2024 12:17:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1718306252; x=1718911052; darn=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=IvrZEAJwQ6yTOLpehlzncq3e3vwChEYXquYHYWTS6KE=; b=Hczpl0+ddfs7V//vNzWAM/yjS+lOUZkl2bAVo851NCii6SNUwHPu83Gc2+3jK4lTcm k1P+3dLb1ZXw7lZgPdZHnYJAfI9VQPSELE21ZMlPn3gU7OF//WESw3EIbYsWS1MA7Ihn RJpJc5VK0MOHqX6hpVO+D/E1i+OwqpJ4BF36VbFZuDuufjE/iSeStWt93iDb+FJFvsX7 uTpc2M3kCWBC2qev96ylxlnln3gLeB2A4E72S3mirDxEZ1KzlWuO6r6eaN0aEgOcX6xV sq+XTu8uJvfBlgD2IVqIfG1+zpn708nMNyHPdOWxfL/8zHUDQlQz+ufb7rp4FQjf1aUX XvqQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1718306252; x=1718911052; 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=IvrZEAJwQ6yTOLpehlzncq3e3vwChEYXquYHYWTS6KE=; b=edzkqBf3CzmjRnRiaEKIkuDO0wds42cgA5wpzSa9ZBfQnCxz9W6f7J1a+HHAUiwn/f 9edO6iZl3s1aJhXfO6fg+yZ7PRllZPHb3nkn0cB832J0c3gT/xhqXeyt/T4E4izwSsdF mPbxzVbsLBZldE/EvwcPaWgwjBBszIk2snH+JtSjeXOJ8v2DiPc1q2q8SZZccH4lKnBq LzI8ZJR85991w1EZqi4glAaBGixrnv9cdhLVgjyafaNGEbrjxIyIv8WAtkeuPMkLOygZ Su4QZwK5BI/KaMWIRjF9WqCdGkOcvD8g9+Flc1R79MrAJ5ODh7igysuhaBXiOH13Np33 rknA== X-Forwarded-Encrypted: i=1; AJvYcCV4V5I5XGBxC1zdQjQn1pTbCUBaZUqma8oGFkMV8NgZJdt66nq1UP0uVpWIyMOF+zpzLWMgZ0pz0chf+ulTlU5nPynxnDxSkI/Q3AtE X-Gm-Message-State: AOJu0YwKT67jXKogVGoa9bJ9x6vZXXjZG8130rCQcuanWjvMSMyjfR43 0kK7gsG2laZzxfpIxDLXziXIfmCqBiDyMPtMDcE2Jhcxcz47oDppu9PLUTAWOsfjYjATRpuA46t LLzgyo4s75HTg2pFS6Txkd9X2gog= X-Google-Smtp-Source: AGHT+IEUU+PPYY7yvbjNm+hzolRohqFZW8Q4gPinFsSyGAykqzHREc23S0+8nwF/bcTe33zuEwAUmMOd5tDCJNcpMpo= X-Received: by 2002:a2e:9153:0:b0:2e9:841d:dacb with SMTP id 38308e7fff4ca-2ec0e6003a9mr4432351fa.40.1718306251634; Thu, 13 Jun 2024 12:17:31 -0700 (PDT) MIME-Version: 1.0 References: <20240610200411.byj6sv2vpgol6wcf@awork3.anarazel.de> <20240612155040.u6cvatdb5tiwcxci@awork3.anarazel.de> In-Reply-To: From: Greg Sabino Mullane Date: Thu, 13 Jun 2024 15:16:54 -0400 Message-ID: Subject: Re: RFC: adding pytest as a supported test framework To: Robert Haas Cc: Jelte Fennema-Nio , Daniel Gustafsson , Andres Freund , Jacob Champion , PostgreSQL Hackers Content-Type: multipart/alternative; boundary="000000000000be7f46061aca599f" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000be7f46061aca599f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Jun 13, 2024 at 9:38=E2=80=AFAM Robert Haas = wrote: > I agree with you, but I'm skeptical that solving it will be as easy as > switching to Python. For whatever reason, it seems like every piece of > infrastructure that the PostgreSQL community has suffers from severe > neglect. Literally everything I know of either has one or maybe two > very senior hackers maintaining it, or no maintainer at all. ... > All of this stuff is critical project infrastructure and yet it feels lik= e > nobody wants to work on > it. I feel at least some of this is a visibility / marketing problem. I've not seen any dire requests for help come across on the lists, nor things on the various todos/road maps/ blog posts people make from time to time. If I had, I would have jumped in. And for the record, I'm very proficient with Perl. Cheers, Greg --000000000000be7f46061aca599f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Thu, Jun 13, 2024 at 9:38=E2=80=AFAM R= obert Haas <robertmhaas@gmail.c= om> wrote:
I agree with you, but I'm skeptical that s= olving it will be as easy as
switching to Python. For whatever reason, it seems like every piece of
infrastructure that the PostgreSQL community has suffers from severe
neglect. Literally everything I know of either has one or maybe two
very senior hackers maintaining it, or no maintainer at all.
...
All of this s= tuff is critical project infrastructure and yet it feels like nobody wants = to work on
it.

I feel at least some of this is a visib= ility / marketing problem. I've not seen any dire requests for help com= e across on the lists, nor things on the various todos/road maps/ blog post= s people make from time to time. If I had, I would have jumped in. And for = the record, I'm very proficient with Perl.

Che= ers,
Greg
=C2=A0
--000000000000be7f46061aca599f--