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 1nFTxb-0000H8-3d for pgsql-bugs@arkaria.postgresql.org; Thu, 03 Feb 2022 04:43:07 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nFTxY-00015k-J8 for pgsql-bugs@arkaria.postgresql.org; Thu, 03 Feb 2022 04:43:04 +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 1nFTxY-00015a-AS for pgsql-bugs@lists.postgresql.org; Thu, 03 Feb 2022 04:43:04 +0000 Received: from mail-il1-x132.google.com ([2607:f8b0:4864:20::132]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nFTxV-00063c-9Y for pgsql-bugs@lists.postgresql.org; Thu, 03 Feb 2022 04:43:03 +0000 Received: by mail-il1-x132.google.com with SMTP id w5so1192793ilo.2 for ; Wed, 02 Feb 2022 20:43:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20210112.gappssmtp.com; s=20210112; h=date:from:to:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=8nHSW9nN4SgwtSF6xwSlp9chPrrIRU+PE1Q9e6jR/ew=; b=f95H7u+jJRWsaC4xGtos+IZL6T5XuRpOrizTkkMaTGFNw0lKqAdjLIt73Od2lJK96l jWrxuUDnyyuzWATR4PepiHWMOb6VWMxdiTUZzG5Bk4qTDoNG3xpRl99oymixBX4f9VYs WCJQ6jBEEOsTeZZMWRxLrCMPv0nyAuQwVCj3YhjCZHLbO3tSGJzOmQ5dvG+62TTG3PY+ P1TW8iUMdyiib9BjmU+LkIYUB7AR57JdaYJTMUbrF0wQTBfUWQ/jCAD3VHHkq0fOtOUN IDuqIBt096ZRoKKiuFDiPDpXnyC4E6qWj1U7N3TMmY6hA+O+7Mes8k/jgJBbbpsqaK3m mI6g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=8nHSW9nN4SgwtSF6xwSlp9chPrrIRU+PE1Q9e6jR/ew=; b=sroqQKgMO4Mqa8rg/oYGfTtu7YM08AvakYDkzDvZScFOph0KrpXfO1NW5KVVTZcflU 55Ef46S8P13ucgOQWZF52WRuRhLi1JHKu5/NKzxZrooTR4aJnkwzCv+4sBZYzu+O1ZEQ O+uFzCaXafZcabZXMqEze4FSrTf/V44bNLmn1aHLD4wwKGchxFJl5YUyoICldvCa8CLJ AELUA5E9dILiSZW0HrgdtxViDqLiQTnzpvmEdbLgumG1JD8bcjPUkR1Koz3Eo7VxtH53 YwOjCs7VNslM70oq8r4ytwdYc+Oy+XmdAy0i5C+WwVSu6ce2Yu5/ZfYPBY0IQcAHYv98 OwDQ== X-Gm-Message-State: AOAM530OAmUL+27L2ynV3V5pXzfTXxbm3MBeN+EWKwIuCelONbyuR7Z2 zVqKm9xV7m1VFAO9fdfFdwSbtA== X-Google-Smtp-Source: ABdhPJzoqh7nj4NkJgen1xPsUydDPAS58LuEj/tWvbXwEHU6B1uyAi+vPsZoCazHW+NDY5QeaH7hXQ== X-Received: by 2002:a92:ca0f:: with SMTP id j15mr11797281ils.189.1643863379217; Wed, 02 Feb 2022 20:42:59 -0800 (PST) Received: from pryzbyj.telsasoft (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id c24sm15142653ioh.40.2022.02.02.20.42.58 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 02 Feb 2022 20:42:58 -0800 (PST) Received: by pryzbyj.telsasoft (Postfix, from userid 1000) id 0B19F800CAB; Wed, 2 Feb 2022 22:42:57 -0600 (CST) Date: Wed, 2 Feb 2022 22:42:57 -0600 From: Justin Pryzby To: padam.tehlan@leptonsoftware.com, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #17384: ERROR: missing chunk number 0 for toast value 152073604 in pg_toast_2619 Message-ID: <20220203044257.GH23027@telsasoft.com> References: <17384-f50f2eedf541e512@postgresql.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <17384-f50f2eedf541e512@postgresql.org> User-Agent: Mutt/1.9.4 (2018-02-28) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Thu, Jan 27, 2022 at 08:57:28PM +0000, PG Bug reporting form wrote: > Issue: ERROR: missing chunk number 0 for toast value 152073604 in > pg_toast_2619 > we are facing issue with mentioned short description error while trying any > operation on database. > > We execute the various commands recommended in various blogs , given > below- > REINDEX table mytable; > REINDEX table pg_toast.pg_toast_40948; > VACUUM analyze mytable; > > Even after successful execution of the above commands, still when execute > the Vacuum full its give error. > > Earlier response will be appreciable. It sounds like the statistics for a catalog table are causing an error.