From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Laura Conrad <lconrad(at)laymusic(dot)org> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: How to restore from pg_dumpall output |
Date: | 2003-02-14 02:04:52 |
Message-ID: | 3200.1045188292@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Laura Conrad <lconrad(at)laymusic(dot)org> writes:
> pg_dumpall -p 8050 >/tmp/db.sql
> I then tried to restore (again as the postgres user), as documented in
> the pg_dumpall man page:
> psql -f /tmp/db.sql template1
> It does a few things, and then says:
> psql:/tmp/db.sql:16: \connect: FATAL 1: IDENT authentication
> failed for user "bostonre"
I believe this will work better if you use "-X use-set-session-authorization"
to pg_dump (which should be the default, but isn't yet). Without that,
you need an authorization configuration that will let you connect as
someone else --- which IDENT won't, superuser or no. (You could set up
an ident map to let that happen, but it'd be tedious if you have lots of
users to keep track of.)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Uday Singh | 2003-02-14 02:57:32 | Can I make Postgresql to bind to 127.0.0.1:5432, instead of all t he available interfaces |
Previous Message | Martin Matusiak | 2003-02-14 01:30:20 | postgresql 7.3 will not start, no error message given |