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 1o6HZc-0000Ji-UZ for pgsql-admin@arkaria.postgresql.org; Tue, 28 Jun 2022 20:12:36 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1o6HZa-0006QX-Qy for pgsql-admin@arkaria.postgresql.org; Tue, 28 Jun 2022 20:12:34 +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 1o6HZa-0006QO-Gx for pgsql-admin@lists.postgresql.org; Tue, 28 Jun 2022 20:12:34 +0000 Received: from mail-pf1-x436.google.com ([2607:f8b0:4864:20::436]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1o6HZY-0007Tk-D5 for pgsql-admin@lists.postgresql.org; Tue, 28 Jun 2022 20:12:33 +0000 Received: by mail-pf1-x436.google.com with SMTP id k9so3762098pfg.5 for ; Tue, 28 Jun 2022 13:12:32 -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:in-reply-to:to; bh=fwKIquyacPs8QKKBFS4r2hNvhfg7xZyLTDjBPWgLgTo=; b=gjHIOu+uPeeVAIFatrbTDTKBxzlnixw9/E501/O6ELZ1b18eZlmU81jVk9SUVZFqOp HwBiY4iTMuNqgQNQgc1Z+1fr2WG2mjWVCnGe0JKxL1WGIBGPnp7GfPmWA89FF0wD97Bv 8pm5OxCuggiUBHc7d83sJ+trBVWLiChaH+wPgc6XTR2/ubZKvdQ3X/Fo4nqER9UwSOwY YuxT527L15AbYH2OHulZcVg87rLpalxXOJVWvBoS2LuerouKuhzUOr7kBZAjdHms4atp 5MKhKPkZ9xx42rRO8ZtjnOkJly3prbXSs4pI5KdEZSgkG5jqiRuZSHP4IVggiylTAOKL r2OA== 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:in-reply-to:to; bh=fwKIquyacPs8QKKBFS4r2hNvhfg7xZyLTDjBPWgLgTo=; b=kw/Pe/fCuAJJmV7GRgqUst0iKAgEP2y0QbrA5LzLVEMHGPkdtBXY2/yOGJWJvfmIG0 NFk+jEHgwP8nzLqcMVFxEnzqD4oAqUruAoSPXK2YUwMfb4x7n1gR076+am6Ya01pGwie 7Hgv0Z4DEcjo/dQ350F8sKlEGpXJN/xlq6MzZ1ZB4qK48XCMpkgUVjQHFMx2+UZRC/zl mOhJ6iYZV4hRoj+q3XIVdwRkqT5tX0FWq0in/VnHxXxUSzjRj+OGx4SlgxQP4UUwuBId ciMvgdgQQtn0T4BhXkigMTScKBR3oBtf1t//+NiHk2kKPE0AJ8EOeJH2Vjj/lx66RZU+ g6ZA== X-Gm-Message-State: AJIora+qzU4AGZE0PzE+BHYaob0lV9lRBSYqFJx53kSSHsPM5NmfAvVF /5s9DpE0x85VoALaHT2C9hHCac5+Unw= X-Google-Smtp-Source: AGRyM1t8/uQ24u/C6RfeQkYUeoc+Hjn7vx8qOIP1jyUql8O9ESVtvp3M5E9matCrp772ppHaolXfdg== X-Received: by 2002:a62:e119:0:b0:525:17bd:a0ad with SMTP id q25-20020a62e119000000b0052517bda0admr5477975pfh.9.1656447150968; Tue, 28 Jun 2022 13:12:30 -0700 (PDT) Received: from smtpclient.apple ([4.42.177.235]) by smtp.gmail.com with ESMTPSA id y41-20020a056a001ca900b00518d06efbc8sm9955265pfw.98.2022.06.28.13.12.30 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 28 Jun 2022 13:12:30 -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:12:29 -0700 Message-Id: <70F022F4-4A35-4F5F-86A1-C5B571253A70@gmail.com> References: <6E89EC2B-D3EF-456A-A020-5A17D44F3103@gmail.com> In-Reply-To: <6E89EC2B-D3EF-456A-A020-5A17D44F3103@gmail.com> To: pgsql-admin@lists.postgresql.org X-Mailer: iPhone Mail (19A404) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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.PGSQ= L.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 12:13 PM, Teja Jakkidi wrot= e: >=20 > =EF=BB=BFHello pgsql-admin, >=20 > I am very new to Postgres and trying to learn how upgrades work in Postgre= s.=20 > We have open source installation and I am wondering if anyone can help me w= ith correct documentation or steps on performing minor and major version upg= rades. >=20 > Thanks, > J. Teja Sri.