Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Wey2q-0003vu-KM for pgsql-admin@arkaria.postgresql.org; Tue, 29 Apr 2014 02:45:20 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1Wey2q-0007ms-41 for pgsql-admin@arkaria.postgresql.org; Tue, 29 Apr 2014 02:45:20 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Wey2p-0007mY-3q for pgsql-admin@postgresql.org; Tue, 29 Apr 2014 02:45:19 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Wey2m-0001nc-QG for pgsql-admin@postgresql.org; Tue, 29 Apr 2014 02:45:18 +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 s3T2jDoT002029; Mon, 28 Apr 2014 22:45:13 -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: <29685.1398725309@sss.pgh.pa.us> Comments: In-reply-to Evan Walter message dated "Mon, 28 Apr 2014 18:38:25 -0500" Date: Mon, 28 Apr 2014 22:45:13 -0400 Message-ID: <2028.1398739513@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: > Thanks for the replies, sorry for not giving more details/background. > The directory is global/26745 OK, so try select relname from pg_class where relisshared and pg_relation_filenode(oid) = 26745; That should tell you which table or index is busted. > It is version 9.1.9 > os is ubuntu on an Amazon ec2 server Um. AWS is, AFAIK, pretty much guaranteed to lose your data eventually. It's a great compute service if you can afford to have nodes fail now and then ... but probably not the best substrate for a database. If you have to use it for that, you *must* have good backup and replication strategies in place. 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