Re: transitioning postgres oid

Actually, if I was able to get the old database up, I wouldn't needed to
re-install postgres again. That is my problem. I could not get the old
databases up and running at all. I had to do a fresh installation. So now
the old databases are just sitting there. Any ideas?

> On Tue, May 14, 2002 at 09:21:37AM -0500, Robert Abbate wrote:
> > This doesn't work because the old databases are not accessible with the
new
> > Postgres installation. I get the following error:
> >
> >
> > Connection to database '26955' failed.
> > FATAL 1: Database "26955" does not exist in the system catalog.
> >
> >
> > Does anyone know how do you update the system catalog to include an old
> > Postges installation OID? I have old databases just sitting there and I
> > can't seem to include them in the new installation. I cannot include
them in
> > the new installation to run pg_dump.
>
> You do pg_dump with the old backend up, then restore to the new one.
> You can automate this by starting (say) the new backend on a different
> port:
>
> pg_dump -c database_name | psql -p new_port database_name
>
>
> A
> --
> ----
> Andrew Sullivan 87 Mowat Avenue
> Liberty RMS Toronto, Ontario Canada
> <andrew(at)libertyrms(dot)info> M6K 3E3
> +1 416 646 3304 x110
>

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.319 / Virus Database: 178 - Release Date: 1/28/02