pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Joseph Shraibman <jks@p1.selectacast.net>
To: Robert Chalmers <robert@chalmers.com.au>
Cc: pgsql <pgsql-sql@postgresql.org>
Subject: Re: Can't access a table. It seems to have been corrupted hsomehow
Date: Mon, 03 Apr 2000 16:28:58 -0400
Message-ID: <38E8FF0A.1F8E940A@selectacast.net> (raw)
References: <004101bf9bb7$354380c0$1a6001cb@chalmers.com.au>

Try vacuuming the database.

Robert Chalmers wrote:

> I have a database with a group of tables in it.
>
> One of the tables seems to have been modified somehow, and no - although I
> can see it with \d I can't actually do anyting to it. Any action, like
> rename, insert, drop gives a message "table doesn't exist". If I try to jsut
> creat it again, it says "can't do that, it already exists!" (words to that
> effect)
>
> So - does it exist or not? How do I actually get rid of that particular
> table all together without destroying the whole database?
>
> bob




view thread (3+ messages)

Message-ID: <38E8FF0A.1F8E940A@selectacast.net>
Permalink:  ../38E8FF0A.1F8E940A@selectacast.net/
Also on:    postgresql.org/message-id/38E8FF0A.1F8E940A@selectacast.net

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-sql@postgresql.org
  Cc: jks@p1.selectacast.net, robert@chalmers.com.au
  Subject: Re: Can't access a table. It seems to have been corrupted hsomehow
  In-Reply-To: <38E8FF0A.1F8E940A@selectacast.net>
  References: <004101bf9bb7$354380c0$1a6001cb@chalmers.com.au> <38E8FF0A.1F8E940A@selectacast.net>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox