Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1o6HbD-0000NH-4w for pgsql-admin@arkaria.postgresql.org; Tue, 28 Jun 2022 20:14:15 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1o6HbB-0002HM-VU for pgsql-admin@arkaria.postgresql.org; Tue, 28 Jun 2022 20:14:13 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1o6HbB-0002H7-LI for pgsql-admin@lists.postgresql.org; Tue, 28 Jun 2022 20:14:13 +0000 Received: from mail-pf1-x430.google.com ([2607:f8b0:4864:20::430]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1o6Hb9-0007UM-6f for pgsql-admin@lists.postgresql.org; Tue, 28 Jun 2022 20:14:12 +0000 Received: by mail-pf1-x430.google.com with SMTP id k9so3765945pfg.5 for ; Tue, 28 Jun 2022 13:14:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=Wbc4TqOO6Zr5R3XE6FUdIO/xIWOdtNdHXd+k82nuHBI=; b=pQraY4gnFW4rfkPtp90BNRPkb9CMIQS0B+mz3C0k8L9uKHIpvekZ9XumdqDqLrI5ip hZQBxehbekDFD22o8q3TNQaqcqoIgaaSOYkHcBoRTaj6XfojGfcQ7xjJUuftEGr6DSxG XT9cmjmMt+nwatVz3WWA+j5N12dLk4TKqSl7xQLIxZmQZO2XOh3hrjylF/lOpxL13TQj TmM9Sk4wQd5Q8asBOfzORH/H0LmMTs4CrEnQz9Byr2QcCbpy2gV7/nn5WpmsCEIpMaTr OFFaAv+yXSYGOlskx9LDCVU0yMkDcWqqMpdMhA3wMrxL/0/yvv56kZVumY6GsRc36OfX zoUg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=Wbc4TqOO6Zr5R3XE6FUdIO/xIWOdtNdHXd+k82nuHBI=; b=gy1bTzbmwzl0pCWYO+0mmxMRsrUjEj9zZPSLNaRkssfeLvWQhwR3fnYpaSIP6FyNIg EAk85JMl2U3v1JJ4DJ4oqQ3GlI3zfbdHNW4tCaXeD3pjdBWeLfAAJP+B9VfHg44pzqMT n5sjBjzmZdcuKm33kUyzWCZ1+31I9swWCRsIxlyHqiDOJCWDK6b+0gMk6xP0AjoostJI 7vpOZSZ2uZrcEPFjwzVzYFmm1s8NBgGF2ACI+pNbkt2T83bBUz/lePZZAOSjtcT7Y+cP yg74JIssxDEaielQR+WLd05uq8xinOf2NKUMsfnuZBG//k3/TJduYuS9RzEKDkGGQTXt W5kA== X-Gm-Message-State: AJIora+/lHmRJhJ12gn1VTuTV04irUp/Igax7KpUhsETOBwKnXQOiI8w YWDBwvnZn3J7/WTPxUXZWbZDnQV3rFA= X-Google-Smtp-Source: AGRyM1uJXQgWDc2Gbqy63Q5Tb8S8k4I9/uWrNcQ9vDPwJlWTubIXhyQhnuoZM+hvLjKRr3f5lP2jdA== X-Received: by 2002:a05:6a00:1995:b0:525:bca8:b066 with SMTP id d21-20020a056a00199500b00525bca8b066mr5389589pfl.16.1656447250008; Tue, 28 Jun 2022 13:14:10 -0700 (PDT) Received: from smtpclient.apple ([4.42.177.235]) by smtp.gmail.com with ESMTPSA id c4-20020a170903234400b0016b9dbcbd51sm54088plh.94.2022.06.28.13.14.09 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 28 Jun 2022 13:14:09 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable From: Teja Jakkidi Mime-Version: 1.0 (1.0) Subject: Re: Postgres open source upgrades Date: Tue, 28 Jun 2022 13:14:08 -0700 Message-Id: References: Cc: pgsql-admin@lists.postgresql.org In-Reply-To: To: Bruce Momjian X-Mailer: iPhone Mail (19A404) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Thank you very much, Momjian. I also tried to test a minor upgrade with online documentation I found. I im= plemented the below steps for upgrading from 14.1 to 14.2 and this is open s= ource. Before upgrade binary location is /postgres/14 1. Stop the cluster 2. Rename old binary location to /postgres/14.old 3. Create new binary location /postgres/14.2 4. Untar the software,=20 Configure in the new directory 14.2 with new unrated software Make world Make install-world 5. Rename /postgres/14.2 to /postgres/14 6. Start the cluster Cluster started and I was able to connect remotely with no issues. However w= hen I tried using psql, I got below error: Connection to server on socket =E2=80=9C/var/run/postgresql/.s.PGSQL= .5432=E2=80=9D failed. But my postgres has been using socket file in /tmp location before upgrade. I= am not sure why after upgrade psql is searching at a different allocation f= or socket.=20 Can someone help me here?=20 Are the steps that I did, correct?? Thanks and Regards, J. Teja Sri. > On Jun 28, 2022, at 1:09 PM, Bruce Momjian wrote: >=20 > =EF=BB=BFOn Tue, Jun 28, 2022 at 12:13:11PM -0700, Teja Jakkidi wrote: >> Hello pgsql-admin, >>=20 >> I am very new to Postgres and trying to learn how upgrades work in Postgr= es.=20 >> We have open source installation and I am wondering if anyone can help me= with correct documentation or steps on performing minor and major version u= pgrades. >=20 > Please look here: >=20 > https://www.postgresql.org/support/versioning/ >=20 > There are links to the documentation there. >=20 > --=20 > Bruce Momjian https://momjian.us > EDB https://enterprisedb.com >=20 > Indecision is a decision. Inaction is an action. Mark Batterson >=20