From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Evan Walter <ewalter(at)decisionanalyst(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: getting a error message when creating temporary table |
Date: | 2014-04-29 02:45:13 |
Message-ID: | 2028.1398739513@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Evan Walter <ewalter(at)decisionanalyst(dot)com> 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
From | Date | Subject | |
---|---|---|---|
Next Message | Albe Laurenz | 2014-04-29 08:09:02 | Re: about the copy command |
Previous Message | Evan Walter | 2014-04-28 23:38:25 | Re: getting a error message when creating temporary table |