migrating administrative pieces to new install
migrating administrative pieces to new install
От:
hal Lynch <hal@sticky.usu.edu>
Дата:
I have both a production machine and a test machine.
The production machine is running 6.5.2 and FreeBSD 3.0.
The test machine is running 6.5.3 and FreeBSD 3.4.
The idea is to migrate all databases from the prod. machine
to the test machine. As soon as the test machine works properly
it will become the prod. machine and vice-versa.
All databases are read(select) only. my pg_hba.conf looks like this:
local all password passwd.
pg_dumpall fails. I haven't found a way to supply a username
and password to the command. The -u flag dosen't work.
pg_dump works but what databases/tables do I dump to get all my
username info.
Any hints for the hintless?
hal
Re: [ADMIN] migrating administrative pieces to new install
От:
Peter Eisentraut <peter_e@gmx.net>
Дата:
On 2000-01-28, hal Lynch mentioned: > All databases are read(select) only. my pg_hba.conf looks like this: > local all password passwd. > > pg_dumpall fails. I haven't found a way to supply a username > and password to the command. The -u flag dosen't work. That's right. Since every database could (in theory) have a completely different authentication scheme, it's not much good to provide a -u option to pg_dumpall. Since pg_dumpall calls pg_dump, it would be possible to make pg_dump recognize when a password is needed automatically. On the other hand I'm more in favour of scrapping pg_dump altogether and rewriting it on of these days. > pg_dump works but what databases/tables do I dump to get all my > username info. The global tables are pg_shadow, pg_group, and pg_database. If they're not too big you might be better off transferring them by hand rather than bothering too much with getting pg_dump[all] to work. Of course, temporarily disabling the password authentication would work as well. -- Peter Eisentraut Sernanders väg 10:115 peter_e@gmx.net 75262 Uppsala http://yi.org/peter-e/ Sweden