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 1tbMF2-00A5B3-HX for pgsql-advocacy@arkaria.postgresql.org; Fri, 24 Jan 2025 16:09:08 +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 1tbMF1-00FmbP-Cl for pgsql-advocacy@arkaria.postgresql.org; Fri, 24 Jan 2025 16:09:07 +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 1tbMF1-00FmbH-5P for pgsql-advocacy@lists.postgresql.org; Fri, 24 Jan 2025 16:09:07 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1tbMEy-001IKS-0m for pgsql-advocacy@lists.postgresql.org; Fri, 24 Jan 2025 16:09:06 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2025010100; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description; bh=VMSFqL8otvU7yjQZvK77ImrMnhnMAODfVmT4VogO3CY=; b=KkUyF uoHIE6cpyD/hcT3jMZaJZJt7vC4QmdtaRT6CXT7qKSgHsa90JiA1palE7r7U2rdE4ktS7DQT4AnYY hLoMUUKZcodqmHOQVEgVzLafyZ06Qknwyoz/lIn8nBbtpZ6oY1bw02T+Uc4NjCgdl9/iLw4duCoUG mb9C9liXBlySR9DMrI1qhOSe1g+uAJW/y/DKa0X7/CIIkF24c5F0a9Bs0fv0mSE+BfHwsxI9CWj3d bix2wxi+lj37WXpf7WZ8Wam38CYvc8X7dvdl30ItybodYGMVqHmXfyTZcCTqNNCYADcTCDbamMVru 2v90PTYSjBRcSi8lrzGBrhSc8uoPQ==; Received: from bruce by momjian.us with local (Exim 4.96) (envelope-from ) id 1tbMEv-0021jC-2F; Fri, 24 Jan 2025 11:09:01 -0500 Date: Fri, 24 Jan 2025 11:09:01 -0500 From: Bruce Momjian To: Christophe Pettus Cc: Vish Penmetsa , Daniel Gustafsson , pgsql-advocacy@lists.postgresql.org Subject: Re: PostgreSql and VMS operating System Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, Jan 24, 2025 at 01:07:56AM -0800, Christophe Pettus wrote: > > > > On Jan 24, 2025, at 01:03, Vish Penmetsa wrote: > > > > Probably I might have misunderstood the purpose of the group or the workings of the postgresql group. > > > > I thought the group will look at suggestions on a voluntary basis review them and if found useful will approve to carry forward with the suggestions. > > > > In this case vmssowftare group provides the os copy on VM's but I thought the group leadership will do some communications. > > The organization of the PostgreSQL Global Development Group is not like the organization of a commercial software organization. It is up to the general developer community to propose, advocate, and see through any changes (including ports). The "leadership" reviews and approves contributions to the primary core PostgreSQL code, but it is up to the person or organization that wants a feature to do the work to make it actually happen. > > So, basically, if you want a maintained VMS port, you need to either drive the project yourself, or find others who will. This email thread from 2003 says VMS probably doesn't work anymore because of lack of testers: https://www.postgresql.org/message-id/flat/200301071531.h07FVWI08147%40candle.pha.pa.us#0dbc1439f51ec7842125fb8ae200b6da I think we worked on VAX/Unix-Posix for many years after that but we eventually removed it. Our normal development flow is: https://wiki.postgresql.org/wiki/Todo#Development_Process Desirability -> Design -> Implement -> Test -> Review -> Commit so I would focus on Desirability at this point. The next question is whether the demand justifies the code changes. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Do not let urgent matters crowd out time for investment in the future.