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.96) (envelope-from ) id 1x0E4x-004X0Y-10 for pgsql-pkg-debian@arkaria.postgresql.org; Sat, 29 Aug 2026 08:06:19 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1x0E4w-00Ar8t-0w for pgsql-pkg-debian@arkaria.postgresql.org; Sat, 29 Aug 2026 08:06:18 +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.96) (envelope-from ) id 1x0E4w-00Ar8l-0C for pgsql-pkg-debian@lists.postgresql.org; Sat, 29 Aug 2026 08:06:18 +0000 Received: from stravinsky.debian.org ([2001:41b8:202:deb::311:108]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1x0E4t-00000002yDg-3BRs for pgsql-pkg-debian@lists.postgresql.org; Sat, 29 Aug 2026 08:06:17 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=debian.org; s=smtpauto.stravinsky; h=X-Debian-User:In-Reply-To:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=vzgA8ncVNdJHQYc4Ny+Pu7vhkXCKLgua3FdPsc/1RHw=; b=jDEVmUGHOZt+EnWxGmX5/dWAZW XU1XnvlYSc6jNgrm2kBCW5ueH+jaGPTqGJNsC/LKCEnqcT/opXmlh3z7vrknacC8Bl3yF1DKtJ78L XjXhyUEUYxkPNz1Gu8keR2UVJdp8P+onvjjTJKp/jCSkPB6dfkByZhWu5+wupOTHxPW2DfCIndakU 48mlGVSqWzlZ7ITPDbAw6jJx0JT/0550rElDn1XODbSMUztmR/00ZRQ8Sw/7s8kLGASjHN1FqAsxX hKWk24zs6rz+A4oH5gD3WNooTbV3vg1SVAX7jSkzklIh1XW7eU0uUPspZ6MXgesmPIiW4EZmDttCp wHL08Y8w==; Received: from authenticated-user by stravinsky.debian.org with esmtpsa (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.96) (envelope-from ) id 1x0E4m-00HPaV-2h; Sat, 29 Aug 2026 08:06:08 +0000 Date: Sat, 29 Aug 2026 10:06:03 +0200 From: Christoph Berg To: Cary Huang Cc: PostgreSQL in Debian Subject: Re: RISC-V support in the PostgreSQL PGDG APT repository Message-ID: References: <1a04a3610dc.4403ea7c7164849.1763647757375446330@highgo.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1a04a3610dc.4403ea7c7164849.1763647757375446330@highgo.ca> X-Debian-User: myon List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Re: Cary Huang > Hi Christoph, > > Hope all is well. This is Cary Huang from Highgo Software, based in Vancouver, Canada. > > I am reaching out to ask whether there are any current or future plans to support > RISC-V (riscv64) in the PostgreSQL PGDG APT repository. > > Are there any major blockers to adding such support today? Hi Cary, thanks for reaching out. The obvious blocker is availability of hardware. We don't have build hosts. The other question would be if those build hosts could keep up with the speed of the other architectures. Currently all supported architectures are about the same speed, so we can build all packages synchronously, which has helped a lot with keeping repository quality up. Looking at Debian's riscv64 build hosts, they are often much slower than the others. > I noticed that Debian 13 already provides PostgreSQL 17 and a number of PostgreSQL > extensions for riscv64, which seems to indicate that PostgreSQL and much of the > ecosystem can already build and run on the architecture. However, PGDG does not > currently provide riscv64 packages, so Debian RISC-V users who need a PostgreSQL > version other than the one shipped by Debian don't really have an official package > source. > > RISC-V adoption is growing, and Canonical's Ubuntu, Red Hat Enterprise Linux, and > Debian now have some initiatives in supporting the RISC-V architecture. I think > having PGDG support could therefore become increasingly useful. HighGo has also > been an active contributor to the PostgreSQL community for many years, and we > would be interested in helping with this initiative. We have connections with the > RISC-V community in China and could potentially help procure suitable hardware or > coordinate other resources if that would be helpful. > > I'd be interested to hear your thoughts and what would be required to make riscv64 > support possible. > > Cary Huang > ------------- > HighGo Software Inc. (Canada) > cary.huang@highgo.ca > www.highgo.ca Christoph