Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WeuLm-00059N-Jj for pgsql-admin@arkaria.postgresql.org; Mon, 28 Apr 2014 22:48:38 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1WeuLl-0003iw-BQ for pgsql-admin@arkaria.postgresql.org; Mon, 28 Apr 2014 22:48:37 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WeuLk-0003ig-A5 for pgsql-admin@postgresql.org; Mon, 28 Apr 2014 22:48:36 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WeuLg-00065V-SR for pgsql-admin@postgresql.org; Mon, 28 Apr 2014 22:48:35 +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 s3SMmTjh029686; Mon, 28 Apr 2014 18:48:29 -0400 From: Tom Lane To: Evan Walter cc: pgsql-admin@postgresql.org Subject: Re: getting a error message when creating temporary table In-reply-to: References: Comments: In-reply-to Evan Walter message dated "Mon, 28 Apr 2014 15:39:30 -0500" Date: Mon, 28 Apr 2014 18:48:29 -0400 Message-ID: <29685.1398725309@sss.pgh.pa.us> X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org Evan Walter writes: > Not sure what is causing this. When we execute: > CREATE TEMPORARY TABLE test(test_code varchar (255)) > We get > ERROR: could not read block 6 in file "global/... " read only 0 of 8192 > bytes What's the exact filename you omitted there, and which PG version is this? I'm guessing this indicates corruption of pg_shdepend or one of its indexes, as that seems like the only shared catalog that's really likely to get touched during a CREATE TEMP TABLE. If you're lucky, it's one of the indexes, and a REINDEX will fix it. Have you had any OS-level crashes lately, power failures, etc? Whatever is corrupted exactly, this shouldn't have happened if filesystem integrity was being maintained properly. regards, tom lane -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin