Re: [ADMIN] migrating administrative pieces to new install - Mailing list pgsql-admin

From Peter Eisentraut
Subject Re: [ADMIN] migrating administrative pieces to new install
Date
Msg-id Pine.LNX.4.21.0001291449430.364-100000@localhost.localdomain
Whole thread Raw
In response to migrating administrative pieces to new install  (hal Lynch <hal@sticky.usu.edu>)
List pgsql-admin
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


pgsql-admin by date:

Previous
From: hal Lynch
Date:
Subject: RE: Suggestions for backup software?
Next
From: Timothy Dyck
Date:
Subject: request for tuning suggestions from PC Week Labs