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 1nhzo3-00021W-NA for pgsql-admin@arkaria.postgresql.org; Fri, 22 Apr 2022 20:23:08 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nhzo2-0004uG-IL for pgsql-admin@arkaria.postgresql.org; Fri, 22 Apr 2022 20:23:06 +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 1nhzo1-0004tq-Dr for pgsql-admin@lists.postgresql.org; Fri, 22 Apr 2022 20:23:06 +0000 Received: from out5-smtp.messagingengine.com ([66.111.4.29]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nhzny-0001Hz-P8 for pgsql-admin@lists.postgresql.org; Fri, 22 Apr 2022 20:23:04 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 89D035C02CA; Fri, 22 Apr 2022 16:23:01 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Fri, 22 Apr 2022 16:23:01 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= quadratum-braccas.com; h=cc:content-type:date:date:from:from :in-reply-to:message-id:mime-version:reply-to:sender:subject :subject:to:to; s=fm2; t=1650658981; x=1650745381; bh=tyRtPjlqGu Qi7PXPs1htef8zrWbU0AQYoPxfMioQEoA=; b=JuK8QhlgrarjdTF9YnlNLPS3rC barq2fr2WOe/I5h2QDXVeBKhWwbJZcTZfhVi4ruOUZchAYuXqimB2vccQFwvbOb+ Sp8zK06Wzo+YYhs1t6nb1W3Gw9uAcBh7bPdI9P/ryBwtAqIr11bihcvTYIa02XW3 vA32zMzjvE8nHj9A+u1Ve3hSqFD/dvT76EDMSBIRnIj+0zDWWDMO5wI0HsnZcR7Y 7E/XGePS5L1tZcU8bEcRzYDP+nqDfLZcfdFC6GFm0lGdHsYoNgFdL/74IAF4AFcR ybu1QwNE5a2QLXGPG4OSj14q9vNAqAJmVYZVsWZADkCRM9YhCEMC9vg0UuUQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:date:from:from :in-reply-to:message-id:mime-version:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; t=1650658981; x=1650745381; bh=tyRtPjlqGuQi7 PXPs1htef8zrWbU0AQYoPxfMioQEoA=; b=oYYeliosO8nNUKEMzNhWYC/Npfj/b cxc/k8qKjwVEM/ys2HT284CGbs8sPNy7Crj8kBm75TN++M+BqASYbATlEc91k4o8 M/Plzi0JCZ+4z6oD8nIAYWyhaPklpkagfD/hJUUyI+uPASJfJnFFU60sT5hMlNFK NIU2JkTSWMz7k9hvlpZq6xo3HO+MwrGV9XqR/aQG4uRu1Ku1VIq/b0WSBr5t7T+f ZK3m39VqxkTIhzp+wSOCIuNxkSptJKDsDq7CXeM2U7clDAikAyL8F6TbOjgvQEj5 JynI+1K2ThCeQzKmZEefrJ1IPhdh50yaHE/xI/IlSGVEvpwloU+gzY+tg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrtdeggddugeejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpegtkfffgggfvffhufesrgdtreertd efjeenucfhrhhomhepufgsohgsuceoshgsohgssehquhgrughrrghtuhhmqdgsrhgrtggt rghsrdgtohhmqeenucggtffrrghtthgvrhhnpeethedvueegvefhveegfeehlefhteetfe dviedviefhjeeuheffkeeufedvjeettdenucevlhhushhtvghrufhiiigvpedtnecurfgr rhgrmhepmhgrihhlfhhrohhmpehssghosgesqhhurggurhgrthhumhdqsghrrggttggrsh drtghomh X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 22 Apr 2022 16:23:01 -0400 (EDT) Content-Type: multipart/alternative; boundary="------------yuiM1g0MIdWPRlyxiI2G7gLI" Message-ID: <938c7425-076f-f752-de61-c5f8f183d24b@quadratum-braccas.com> Date: Fri, 22 Apr 2022 14:23:00 -0600 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.8.0 To: Pgsql-admin Content-Language: en-US From: Sbob Subject: could not read block 0 in file Error List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------yuiM1g0MIdWPRlyxiI2G7gLI Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Hi all; We had an issue with a PostgreSQL v12 cluster. Not sure all of the history as I was pulled in late, however we were seeing that the db would not start due to WAL inconsistencies, was throwing an error about could not find wal records. So we ran a pg_resetwal -f -D [data dir] we are dumping (via pg_dump) all the databases in the broken cluster and I will restore them to a new cluster, however in one of the databases, for one of the tables we are getting this: pg_dump: error: Dumping the contents of table "bigtable" failed: PQgetResult() fai led. pg_dump: error: Error message from server: ERROR:  could not read block 0 in file "base/6328739/6340053": read only 0 of 8192 bytes pg_dump: error: The command was: COPY public.bigtable (recordid, containerid, record_type, description, overlaygroup) TO stdout; Is there any way to recover? Thanks in advance --------------yuiM1g0MIdWPRlyxiI2G7gLI Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit

Hi all;


We had an issue with a PostgreSQL v12 cluster. Not sure all of the history as I was pulled in late, however we were seeing that the db would not start due to WAL inconsistencies, was throwing an error about could not find wal records.

So we ran a pg_resetwal -f -D [data dir]


we are dumping (via pg_dump) all the databases in the broken cluster and I will restore them to a new cluster,

however in one of the databases, for one of the tables we are getting this:


pg_dump: error: Dumping the contents of table "bigtable" failed: PQgetResult() fai
led.
pg_dump: error: Error message from server: ERROR:  could not read block 0 in file "base/6328739/6340053": read only 0 of 8192 bytes
pg_dump: error: The command was: COPY public.bigtable (recordid, containerid, record_type, description, overlaygroup) TO stdout;



Is there any way to recover?


Thanks in advance


--------------yuiM1g0MIdWPRlyxiI2G7gLI--