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 1qlPLp-002euX-Pk for pgsql-admin@arkaria.postgresql.org; Wed, 27 Sep 2023 07:52:53 +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 1qlPLo-001FZ8-Et for pgsql-admin@arkaria.postgresql.org; Wed, 27 Sep 2023 07:52:52 +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.94.2) (envelope-from ) id 1qlPLo-001FYj-0G for pgsql-admin@lists.postgresql.org; Wed, 27 Sep 2023 07:52:52 +0000 Received: from mail-wm1-x332.google.com ([2a00:1450:4864:20::332]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qlPLh-006t3C-5G for pgsql-admin@lists.postgresql.org; Wed, 27 Sep 2023 07:52:50 +0000 Received: by mail-wm1-x332.google.com with SMTP id 5b1f17b1804b1-40572aeb73cso73012825e9.3 for ; Wed, 27 Sep 2023 00:52:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20230601.gappssmtp.com; s=20230601; t=1695801163; x=1696405963; darn=lists.postgresql.org; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:to:from:subject:message-id:from:to:cc:subject:date :message-id:reply-to; bh=ECeg7BCEvNizKF9Pa3t/iDqyhKjMmgtuN/xXiWH0ANI=; b=ZVpMSz+EKP+DxGLTT5I/BH+UDKUlvFCeaqG788E0lbOv6XIsR3mu3h2DKuP0Br9sk4 1DPW8z8gR8wmpsGpUeZ/CYM2lTHpNFVxkMFiCKGCGaQa+rzOBp4HKr8l2zso24juX7Pr 5Gnk2EhEwR47AvPjnAiCDv3KKcttkH/FJ2m0VMa6SIBv584rz19oOXhSP5puyQpqqXs3 Jo3VyI2J1NT7ROncxKnnDHXnnoqhPSMqx5vzGLTkRxzEBK6tPmDBaRiJkRjXJIC50b+F gLB8MM5ABJFZzPGglZlXQg7FH+DH+OiQXRqWZ38eYUeDFCGwZpFeDvEZQM5N0kHghCIR 7gfA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1695801163; x=1696405963; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:to:from:subject:message-id:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=ECeg7BCEvNizKF9Pa3t/iDqyhKjMmgtuN/xXiWH0ANI=; b=SxIwuMgQ6kRd43locptBJvItDz7jWbigBDgTSRG1XclUbC/G05g1AJ+shSgjRuSCQM X/MGU2T/Gcb6zjDzGqv77OO6laJvbCyNTSq8UieLcD3wmsv4QEy/2lbUdGx0d4rLqfas joFiVlN2QhDSNG4f7uMBBdpTjMa9vbqmxiTV/HLW1q+4M/yqa9zIFKGFE0VYSI4x3OBS yQkTYowPbu3ZGq4C50OOZkALG6ikRwCx+NgO+uLVIqsH+38w59QfeK/xq8aSdr6joq/K 3CysYhaI4e9c/1xM6U/jgnN98wuuOkjDPBSgYN6i3OBOTxplnzSkovkt5mCTCUthxeQ9 riIw== X-Gm-Message-State: AOJu0Yzjpj6LzaJX4ATj0u2oW5Z9uNVAx357pdC9UkJpj9VhklPti6AU q5lf82AsKER31JaK6Pg++Hf0BjumBmMtRgbAn6Y= X-Google-Smtp-Source: AGHT+IFcWELexeBRJlHiyG/mzFGSQYH/K8NUfl7SWVbXTKPHgYhEx89uUS929EMWZk3aE4+GLGpD2g== X-Received: by 2002:a05:600c:2054:b0:406:177e:5de8 with SMTP id p20-20020a05600c205400b00406177e5de8mr1123969wmg.35.1695801163197; Wed, 27 Sep 2023 00:52:43 -0700 (PDT) Received: from localhost.localdomain (178-190-177-111.adsl.highway.telekom.at. [178.190.177.111]) by smtp.gmail.com with ESMTPSA id 22-20020a05600c22d600b0040648217f4fsm150474wmg.39.2023.09.27.00.52.42 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 27 Sep 2023 00:52:42 -0700 (PDT) Message-ID: <181619eddd09e4a23568d748bc5d2504c0a496ad.camel@cybertec.at> Subject: Re: Corruption issue From: Laurenz Albe To: OS DB2 , Pgsql-admin Date: Wed, 27 Sep 2023 09:52:42 +0200 In-Reply-To: References: <1D460E80-E3B1-493D-9801-A34DD9657CA2@jakobs.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.48.4 (3.48.4-1.fc38) MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Wed, 2023-09-27 at 11:16 +0530, OS DB2 wrote: > > > > On Fri, Sep 22, 2023, 12:48 PM OS DB2 wro= te: > > > > > In one of the our production database when we are trying to fetch= the > > > > > records from one of the table, we are getting below error. > > > > >=20 > > > > > Compressed data is corrupted > > > > >=20 > > > > > Os - linux > > > > > Postgresql version - 9.5 > > What can be the cause of corruption? You wrote 9.5, but you didn't disclose how old your hardware or your operating system are. Most often the cause is bad hardware, but it could be a bug in the file sys= tem or the Linux kernel or one of the numerous bugs that have been fixed in PostgreSQL since 9.5 went out of commission. Yours, Laurenz Albe