Wouldn't it be better to do a pg_dump from the source database, and then load
that dump file into the new machine? It should fix a lot of these
problems....
-Jason
"Robert G. Fisher" <[EMAIL PROTECTED]> on 03/09/2000 10:42:32 AM
To: [EMAIL PROTECTED]
cc:
bcc:
Subject: [GENERAL] Listing Tables Query?
I'm relatively new to using PostgreSQL, I've been toying with
it on my home machine but now am also using it in the office.
In this scenario, rather than creating a DB, I am copying
in the database from another site -- this is simply a tar
of the directory tree under /usr/local/pgsql/base rather
than a dump of the db.
I'm at the point where I've compiled PostgreSQL 6.5.3 and
untarred the file -- then gone in and used update queries
to change the uid of the old postgres user to my current
postgres uid in the following tables and fields combinations:
pg_aggregate -> aggowner,
pg_am -> amowner,
pg_class -> relowner,
pg_operator -> oprowner,
pg_type -> typowner
Thus I no longer get the error message cannot cache user '1002'
(the old id) and \dS returns the system tables. However,
\dt will return that it can not find any tables -- but I can
issue a select on these tables that reportedly don't exist
such as 'select * from cart' and although the table is empty,
I do at least get the list of fields.
Can anyone help me understand what's going on or point me at
the appropriate documentation?
--
Robert G. Fisher NEOCOM Microspecialists Inc.
System Administrator/Programmer (540) 666-9533 x 116
