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 1rfpn1-002bT5-08 for pgsql-announce@arkaria.postgresql.org; Thu, 29 Feb 2024 23:26:11 +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 1rfpmz-009acm-I8 for pgsql-announce@arkaria.postgresql.org; Thu, 29 Feb 2024 23:26:10 +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 1rfpmy-009ace-Mm for pgsql-announce@lists.postgresql.org; Thu, 29 Feb 2024 23:26:09 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rfpmv-002A91-KW for pgsql-announce@lists.postgresql.org; Thu, 29 Feb 2024 23:26:08 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:Date:Reply-To:From:To:Subject: MIME-Version:Content-Type:Sender:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:In-Reply-To:References; bh=NU3ycAnhAN8DmCUYawbiRdM1U9Mc5Yl5glSj7IVVKuY=; b=yA9zshhy9FzLx5vlVvUoH0vMVR 16LauF8LUQuWy0PXnH8x3Ae+aUCpqqU39uVfObrDs9MqJ18gA3ayzlmxi8Vb6fh648urzZUllfBqc advv/cUWt2TYn7sC/5ITSbKdNWnLP738xeZYCW0b15j1gncz1sdpoJ/R/nX5FCiQUyziRJJjIPlk2 4dIRuH+czgpE1BmBuQ3+YNiAR+OIuj0w0AV6PukRhwXUyKsFREbR66+o/dXHIoeAgNuG3Wy1m1Zy6 cXlXS0al1w/M+22e4i4NgGfiUACoxHL/Ftyk9TFgMKa10KqejlLO4CvEp/VGJKpMqd5xkhy/G/+f4 RUygrn6A==; Received: from wrigleys.postgresql.org ([2a02:c0:301:0:ffff::34]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rfpmt-004mPM-Ez for pgsql-announce@lists.postgresql.org; Thu, 29 Feb 2024 23:26:04 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rfpmr-00COnE-Pd for pgsql-announce@lists.postgresql.org; Thu, 29 Feb 2024 23:26:02 +0000 Content-Type: multipart/mixed; boundary="===============6981344442643714840==" MIME-Version: 1.0 Subject: =?utf-8?q?Installing_PostgreSQL_on_SLES_15_just_got_easier_=E2=80=93_and_better!?= To: PostgreSQL Announce From: PostgreSQL PGDG RPM Repository via PostgreSQL Announce Reply-To: devrim@gunduz.org Date: Thu, 29 Feb 2024 23:25:20 +0000 Message-ID: <170924912075.645.11791095499829247470@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-pglister-tags: pgsql X-pglister-tagsig: 0ff12fc76ea8a87427675d7cd24786c0aaa8829b076b76a32ed11029c5a592e3 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --===============6981344442643714840== Content-Type: multipart/alternative; boundary="===============3076426810398651459==" MIME-Version: 1.0 --===============3076426810398651459== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable [The PostgreSQL RPM repository for SuSE Enterprise Linux](https://zypp.post= gresql.org) has supported SLES for quite some time. We followed the usual = conventions and used zypper addrepo =E2=80=A6 to add the repositories. This method mostly works, however it is (now, was=E2=80=A6) not easy for us= to make modifications to the repository files. This led to multiple issues= in the past like not being able to add a common repository, not being abl= e to archive old repos properly or not being able to change signatures, etc= . We do not have this problem in the [PostgreSQL YUM/DNF repository](https:= //yum.postgresql.org/) because it already has [repository RPMs](https://yu= m.postgresql.org/repopackages/) .=20 Good news: [We now have the same infrastructure in the SLES 15](https://zyp= p.postgresql.org/howtozypp/) ! Please note that this will have a direct ef= fect on the directory layout so the package locations will change for some = of the packages (i.e. [=E2=80=9Ccommon=E2=80=9D packages](https://download= .postgresql.org/pub/repos/zypp/common/)) . It means all of the SLES 15 use= rs will need to switch to the new repository RPMs at the earliest convenien= ce to receive the updates or even install many of the packages. As an unintentional good side effect of this change, [=E2=80=9Cextras=E2=80= =9D repository is now available also on SLES 15](https://zypp.postgresql.or= g/news/new-repo-extra-packages/) . This extras repo provides packages to su= pport Patroni. Here is a quick FAQ: 1. How can I switch to the new repository RPM? `zypper install https://download.postgresql.org/pub/repos/zypp/reporpm= s/SLES-15-x86_64/pgdg-suse-repo-latest.noarch.rpm` 2. I am a new user. How does it affect me? =20 Not at all. Just follow the instructions and install PostgreSQL as usu= al: `https://zypp.postgresql.org/repopackages/` 3. Can I disable specific PostgreSQL releases? Yes. You can run this command to disable PostgreSQL 12 repo: `zypper mr -d pgdg-12` --===============3076426810398651459== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Installing PostgreSQL on SLES 15 just got easier =E2=80=93 and b= etter!
 

Installing PostgreSQL on SLES 15 just got easier =E2=80=93 and better= !

The PostgreSQL RPM reposi= tory for SuSE Enterprise Linux has supported SLES for quite some time.= We followed the usual conventions and used zypper addrepo =E2=80=A6 to add= the repositories.

This method mostly works, however it is (no= w, was=E2=80=A6) not easy for us to make modifications to the repository fi= les. This led to multiple issues in the past like not being able to add a = common repository, not being able to archive old repos properly or not bein= g able to change signatures, etc. We do not have this problem in the PostgreSQL YUM/DNF repository because it already has repository RPMs .

Good news: We = now have the same infrastructure in the SLES 15 ! Please note that thi= s will have a direct effect on the directory layout so the package location= s will change for some of the packages (i.e. =E2=80=9Ccommon=E2=80=9D packages) . It means all of t= he SLES 15 users will need to switch to the new repository RPMs at the earl= iest convenience to receive the updates or even install many of the package= s.

As an unintentional good side effect of thi= s change, =E2=80=9Cextras= =E2=80=9D repository is now available also on SLES 15 . This extras rep= o provides packages to support Patroni.

Here is a quick FAQ:

  1. How can I switch to the new repository RPM?=

    zypper install https://download.postg= resql.org/pub/repos/zypp/reporpms/SLES-15-x86_64/pgdg-suse-repo-latest.noar= ch.rpm

  2. I am a new user. How does it affect me?

    Not at all. Just follow the instructions an= d install PostgreSQL as usual: https://zypp.postgresql.org/repopackag= es/

  3. Can I disable specific PostgreSQL releases?=

    Yes. You can run this command to disable Po= stgreSQL 12 repo:

    zypper mr -d pgdg-12
This email was sent to you from PostgreSQL PGDG RPM Repository. It was deli= vered on their behalf by the PostgreSQL project. Any questions about the content of the message shou= ld be sent to PostgreSQL PGDG RPM Repository.

You were sent this email as a subscriber of the pgsql-announce mai= linglist, for the content tag PostgreSQL Project. To unsubscribe from further emails, or change which emails you want to receive, please click th= e personal unsubscribe link that you can find in the headers of this email, or visit https://lists.postgresql.org/unsubscribe/.
 
--===============3076426810398651459==-- --===============6981344442643714840==--