Mary Ellen Fitzpatrick <[EMAIL PROTECTED]> writes:
> I am trying to run pg_dump on the database with the corrupt table, and
> try to restore the database. I also tried to vacuumdb the database and
> get the same error.
> I get the following error.
> pg_dump
> pg_dump: query to o
I am trying to run pg_dump on the database with the corrupt table, and
try to restore the database. I also tried to vacuumdb the database and
get the same error.
I get the following error.
pg_dump
pg_dump: query to obtain list of data types failed: PANIC: read of clog
file 100
On 8/10/07, Mary Ellen Fitzpatrick <[EMAIL PROTECTED]> wrote:
> Merlin,
>
> I am willing to spend the time, as it is an important table. I am a
> newbie at this and it has fallen into my lap.
> From what the user tells me, it is only the one table.
> Not sure if fsync was running, how can I tell?
On 8/10/07, Mary Ellen Fitzpatrick <[EMAIL PROTECTED]> wrote:
> Hi,
>
> We are running postgresql-7.3.3 and we had a hardware controller and
> disk failure on the system. And of course the database does not appear
> to be backup anywhere.
>
> I was reading about PITR and was wondering if that is a
Hi,
We are running postgresql-7.3.3 and we had a hardware controller and
disk failure on the system. And of course the database does not appear
to be backup anywhere.
I was reading about PITR and was wondering if that is applicable to my
version. We do have pg_xlog files and I am wondering
