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 1pRJPD-0008Ja-S5 for pgsql-admin@arkaria.postgresql.org; Sun, 12 Feb 2023 20:57:04 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pRJPC-0001sQ-0r for pgsql-admin@arkaria.postgresql.org; Sun, 12 Feb 2023 20:57:02 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pRJPB-0001sG-JD for pgsql-admin@lists.postgresql.org; Sun, 12 Feb 2023 20:57:01 +0000 Received: from mail-qt1-x82f.google.com ([2607:f8b0:4864:20::82f]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1pRJP4-0000Qc-Ot for pgsql-admin@lists.postgresql.org; Sun, 12 Feb 2023 20:57:01 +0000 Received: by mail-qt1-x82f.google.com with SMTP id c2so11947263qtw.5 for ; Sun, 12 Feb 2023 12:56:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-language:thread-index:mime-version:message-id:date:subject :to:from:from:to:cc:subject:date:message-id:reply-to; bh=b1Ppo/xDzgxvbDH2oGsZV/lSHcYhb3kaY8wi69bFWN8=; b=ajE9e+5A0/LhPhAh30+cZF/zhrHYPoL8mU0I4gelPBlKoaQXZBb5hVNNQG9Isrmx/C JCfrF9nkZ8AK0Jyte3yWOxc6k2paXi1w1jZJT+RcWx6PZMokGRq1uuAyXEpsxUCsEiyK AkR/GZalXHTGP8m79uf27upW11HBCxsccQPxhCIHeWHQwX/wO/fVFlbEfpCtMu25x9ac urnO10bo1pdYuR8Re2CiWRIPf949EmWiGlstuQbcq+iDq8cZpdt6X/N+KlSaxLR/GnfR zeMTR5vNfFFMeL4qdGceFrQDYCyKybFGHup+nyX4cqp84LQqsRENGG8Dtv9DRbVtUtyf NYJw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-language:thread-index:mime-version:message-id:date:subject :to:from:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=b1Ppo/xDzgxvbDH2oGsZV/lSHcYhb3kaY8wi69bFWN8=; b=G8q14I2qDG0SUbn3XBejAKZqjE1LqvMTvlG0C40xuYxb95nEB2ngMkXH3zR5WHNsCj H4QQ5J6XkYTEqaAHHQ3X7PSBAmoSZlCDVAjl4KRZzifTX8Ep7ehpWb0P5At8529YzDeU +GOPDtUqKsm81tTdY7pIGE+FkUYr819XW7O2/Vs7aKUFkUhwxA6M/5hj4lsZjAvza4qZ VpZdwJeU5r5m4T25H+aNZR1alzmwhp+RrhdAkyiGyrPZv7CP3uguD/tE7mVGVj8pp90e OlfDFFwlftyMaPI3RY4CBS7Jm5I/MoP0ETXiQrmjIVp3CROO3wiun1V3U5rLoI4SYRbv F+QA== X-Gm-Message-State: AO0yUKX75c/c3cZVqI1iGs7napsRhr7zftlFq+HHT3ZZqvz1i7U5pBRK eIzQTNGJnGNyTNKoNRqmbhq1sGvgzM+5xf765vw= X-Google-Smtp-Source: AK7set+FOsQYgPtxlacKDj23F3eoTaRXlgFKMwwjo4OO9l4/QaDk7ILeO5/Cokh03M+cPZuvm7sgQg== X-Received: by 2002:a05:622a:44d:b0:3bc:d0de:6adf with SMTP id o13-20020a05622a044d00b003bcd0de6adfmr10673627qtx.31.1676235412403; Sun, 12 Feb 2023 12:56:52 -0800 (PST) Received: from GHHPN ([40.85.155.127]) by smtp.gmail.com with ESMTPSA id e11-20020ac8010b000000b003b62e9c82ebsm8066390qtg.48.2023.02.12.12.56.51 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 12 Feb 2023 12:56:52 -0800 (PST) From: To: Subject: Upgrade from PostGIS 2.3 to 2.5.5 in PostgreSQL 11 error Date: Sun, 12 Feb 2023 23:56:45 +0300 Message-ID: <000301d93f24$85fa3480$91ee9d80$@gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0004_01D93F3D.AB476C80" X-Mailer: Microsoft Outlook 16.0 Thread-Index: Adk/JFVMFfdF6TL5Rga/DOGadpPCEg== Content-Language: en-us List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multipart message in MIME format. ------=_NextPart_000_0004_01D93F3D.AB476C80 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Dear all, I'm facing an issue while upgrading from PostGIS 2.3 to 2.5.5 in PostgreSQL 11. I used the following command to upgrade the extension: ALTER EXTENSION postgis UPDATE; However, after executing the command and exiting the psql terminal, the database went down and the logs showed the following error: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory I've tried to restore the database from a recent backup, but the issue persists. I'm seeking help from the community to resolve this issue. I would be grateful if someone could assist me with resolving this issue. I'm available to provide any additional information or logs that may be helpful. Thank you for your time and support. Best regards, Ghadeer. ------=_NextPart_000_0004_01D93F3D.AB476C80 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Dear all,

 

I'm facing = an issue while upgrading from PostGIS 2.3 to 2.5.5 in PostgreSQL 11. I = used the following command to upgrade the extension:

ALTER EXTENSION postgis = UPDATE;

However, after = executing the command and exiting the psql terminal, the database went = down and the logs showed the following error:

The postmaster has commanded this server process to = roll back the current transaction and exit, because another server = process exited abnormally and possibly corrupted shared = memory

I've tried to restore = the database from a recent backup, but the issue persists. I'm seeking = help from the community to resolve this issue.

 

I would be = grateful if someone could assist me with resolving this issue. I'm = available to provide any additional information or logs that may be = helpful.

 

Thank you for your time and support.

 

Best = regards,

Ghadeer.

------=_NextPart_000_0004_01D93F3D.AB476C80--