From: Tom Lane <tgl@sss.pgh.pa.us>
To: Lukasz Brodziak <lukasz.brodziak@gmail.com>
Cc: pgsql-admin@postgresql.org
Cc: pgadmin-support@postgresql.org
Subject: Re: [ADMIN] Can't access tables.
Date: Wed, 06 Oct 2010 09:41:16 -0400
Message-ID: <15455.1286372476@sss.pgh.pa.us> (raw)
In-Reply-To: <AANLkTinWHJn+9BxR1XOcqw8LLxru6MyXEUEV0kiVkTkx@mail.gmail.com>
References: <AANLkTinWHJn+9BxR1XOcqw8LLxru6MyXEUEV0kiVkTkx@mail.gmail.com>
Lukasz Brodziak <lukasz.brodziak@gmail.com> writes:
> I have a problem with viewing tables from my DB. The interesting thing
> is that the physical files exist in the data folder but only some of
> them are visible both in pgAdmin and the application that uses the DB.
> What's more there's no trace of those tables in pg_class whatsoever. I
> can view ca. half of the tables (120 out of almost 250). Have anyone
> come accross such behaviour? The files appear to be fine compared to
> another DB containing same tables and same data.
We used to get reports of that sort of thing from people who hadn't
vacuumed pg_class in a very long time (>2 billion transactions).
The pg_class rows *were* there, but invisible to ordinary queries
because of wraparound. That should be impossible in any modern
PG release branch, but since you didn't say what you're running,
maybe vacuuming the system catalogs would help.
regards, tom lane
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 using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, lukasz.brodziak@gmail.com, pgadmin-support@postgresql.org
Subject: Re: [ADMIN] Can't access tables.
In-Reply-To: <15455.1286372476@sss.pgh.pa.us>
* 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