Re: COPY does not work with regproc and aclitem

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: COPY does not work with regproc and aclitem
Date: 2006-10-23 20:22:52
Message-ID: 28143.1161634972@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> writes:
> I'm playing with catalog upgrade. The very basic idea of my experiment
> is export data from catalog and import it back to the new
> initialized/fresh catalog.

That is never going to work, at least not for any interesting catalogs.
A system with a "fresh" (I assume you mean empty) pg_proc, for instance,
is non functional.

A much bigger problem, if you're thinking of this as a component step
of pg_upgrade, is that you can't use anything at the COPY level of
detail because it will fail if the new version wants a different catalog
layout --- for instance, if someone's added a column to the catalog.
The right way to implement pg_upgrade is to transfer the catalog data
at the SQL-command level of abstraction, ie, "pg_dump -s" and reload.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-10-23 20:27:01 Re: COPY does not work with regproc and aclitem
Previous Message Andrew Dunstan 2006-10-23 20:17:55 Re: COPY does not work with regproc and aclitem

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2006-10-23 20:27:01 Re: COPY does not work with regproc and aclitem
Previous Message Andrew Dunstan 2006-10-23 20:17:55 Re: COPY does not work with regproc and aclitem