Re: pg_dump error

From: Philip <silvermaple(at)usermail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: pg_dump error
Date: 2004-05-24 14:30:10
Message-ID: 20040524093010.48a82545.silvermaple@usermail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

At some time fairly close to Sun, 23 May 2004 23:09:20 -0400,
rumor has it that Tom wrote:

> Philip <silvermaple(at)usermail(dot)com> writes:
> > Okay, now I'm stumped! Since I don't even know what "pga_images" is
> > for I don't no how much trouble I'm in!
>
> Not a lot; that's not a system catalog but something that PgAccess
> creates. If you're not using PgAccess anymore, you can probably just
> drop the table and you're done. If you are, your best bet is to drop
> all the pga_foo tables so that PgAccess will recreate them all when
> you next start it.
>
> BTW, 7.2 is pretty ancient. You should update to at least 7.2.4.
>
> regards, tom lane

Thanks Tom!! I really don't like to panic unless there is good reason
for it...

I'll upgrade to 7.2.4 and see if I can figure out how to drop some
tables...

Philip

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Dane Dwyer 2004-05-24 14:35:03 vacuumdb: vacuuming of database "xxx" failed: ERROR: failed to re-find parent key in "pg_class_relname_nsp_index"
Previous Message Greg Stark 2004-05-24 14:06:56 Re: Combining several rows