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 1tbMQf-00A6eO-NB for pgsql-advocacy@arkaria.postgresql.org; Fri, 24 Jan 2025 16:21:10 +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 1tbMQe-00Fuzk-Cl for pgsql-advocacy@arkaria.postgresql.org; Fri, 24 Jan 2025 16:21:08 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tbMQe-00FuzZ-5F for pgsql-advocacy@lists.postgresql.org; Fri, 24 Jan 2025 16:21:08 +0000 Received: from smtp94.iad3a.emailsrvr.com ([173.203.187.94]) by makus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1tbMQY-001INk-28 for pgsql-advocacy@lists.postgresql.org; Fri, 24 Jan 2025 16:21:07 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=pgexperts.com; s=20190219-ofqv31v6; t=1737735662; bh=h3oMKDATj1iRIZm9YV1Bgl8de2+YAPxjp467zBcvFb4=; h=Subject:From:Date:To:From; b=MuuzZSMfGlGnUEuzQ3Bo2PDXsWTmUl83wGlu3GqBZyis+iGLjuIBb6Q4qYz7BL3sc PDIHlSAgohId5DjibKgKnFS2TCK1wKThj/+MgWKLMvh8tCihLmn7H8KyYNMoIQmPsy rlNG/G/UEPsogXwQlW5fCwezF9FFuSmrSoHVatlY= X-Auth-ID: christophe.pettus@pgexperts.com Received: by smtp36.relay.iad3a.emailsrvr.com (Authenticated sender: christophe.pettus-AT-pgexperts.com) with ESMTPSA id A5920559B; Fri, 24 Jan 2025 11:21:01 -0500 (EST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51\)) Subject: Re: PostgreSql and VMS operating System From: Christophe Pettus In-Reply-To: Date: Fri, 24 Jan 2025 08:20:30 -0800 Cc: Daniel Gustafsson , pgsql-advocacy@lists.postgresql.org, Bruce Momjian Content-Transfer-Encoding: quoted-printable Message-Id: <3CD15C4F-5050-47AB-A2A2-FD491381CC53@pgexperts.com> References: To: Vish Penmetsa X-Mailer: Apple Mail (2.3776.700.51) X-Classification-ID: c2b2d0d7-0d4b-47b9-afd1-aa132ded619b-1-1 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On Jan 24, 2025, at 08:09, Bruce Momjian wrote: > Our normal development flow is: >=20 > https://wiki.postgresql.org/wiki/Todo#Development_Process > Desirability -> Design -> Implement -> Test -> Review -> Commit >=20 > so I would focus on Desirability at this point. The next question is > whether the demand justifies the code changes. To expand on this just a bit, you do not need anyone's permission to = just take the existing PostgreSQL code base and get it running on VMS. = PostgreSQL is much more truly open-source than a lot of "open source" = projects. However, what you then have is a fork, rather than the = mainline PostgreSQL codebase. Since it is extremely unlikely that you = can just compile the current code on VMS and have it work, some patches = will be required to do conditional compilation and provide support code = for VMS, and perhaps some additions to and modifications of the = documentation and test suite. The part where you need to negotiate with the community is whether or = not to accept those changes back into the mainline. To be extreme, if = the difference is one small conditionally-compiled primitive and the = code otherwise runs just as it did before (including performance) on the = currently-supported platforms, the chance is pretty good; if there is = extensive surgery that requires a lot of changes, or if those changes = have performance or maintenance impact on the mainline, the chance is = much lower. -- Christophe Pettus / christophe.pettus@pgexperts.com Chief Executive Officer / PGX Inc. / 24x7 Support, Consulting, = Development / pgexperts.com See us at: SCaLE, March 6-9, Los Angeles / Nordic PgDay, Copenhagen, = March 18