Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eWl5f-0007DU-7p for pgsql-admin@arkaria.postgresql.org; Wed, 03 Jan 2018 15:36:27 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eWl5e-0001gS-OM for pgsql-admin@arkaria.postgresql.org; Wed, 03 Jan 2018 15:36:26 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1eWl5e-0001gJ-Eo for pgsql-admin@lists.postgresql.org; Wed, 03 Jan 2018 15:36:26 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1eWl5c-0005cW-54 for pgsql-admin@lists.postgresql.org; Wed, 03 Jan 2018 15:36:25 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id w03FaLHX013293; Wed, 3 Jan 2018 10:36:21 -0500 From: Tom Lane To: Jorge Daniel cc: "pgsql-admin@lists.postgresql.org" Subject: Re: pt_toast table seems to be In-reply-to: References: Comments: In-reply-to Jorge Daniel message dated "Wed, 03 Jan 2018 15:25:22 +0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <13291.1514993781.1@sss.pgh.pa.us> Date: Wed, 03 Jan 2018 10:36:21 -0500 Message-ID: <13292.1514993781@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Jorge Daniel writes: > [ repeated corruption of a pg_toast index ] That's pretty interesting. What PG version is this exactly? If you could put together a self-contained test case based on your environment, I'm sure we'd be happy to try to isolate how the corruption is occurring. Even with random OOM kills, PG is not supposed to leave you with a corrupt index, so I'd say there's a bug in there somewhere. regards, tom lane