From: | Artur Pietruk <arturp(at)plukwa(dot)pdi(dot)net> |
---|---|
To: | Darren McClelland <darren(at)zonarsystems(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Automated database backups and authentication |
Date: | 2002-08-06 21:34:58 |
Message-ID: | 20020806213458.GF996@yoda.plukwa.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Tue, Aug 06, 2002 at 11:39:03AM -0700, Darren McClelland wrote:
> Thanks, that's an idea. I'd always been thinking of ident as unreliable, but
> if I control the authenticating server then it's something usable. At least I
[cut]
Well, if you want to use ident that way, than you have to trust not
only those two servers, but all hosts in their network segments - do not
forget about ARP poisoning.
I think, that in your setup it would be better to do crypt=-auth
and:
- use PGPASSWORD environment variable, just set it before you execute
pg_dumpall. Go and check pgsql-admin list archives - I remember that lately
PG developers stated that PGPASSWORD variable may not be available in the
next PG release - but in that case there will be other way to give password.
Also check online docs: http://www.postgresql.org/idocs/index.php?libpq-envars.html.
OR:
- you can try to pass password to pg_dumpall through tricks like:
"echo mypass | pg_dumpall .... "
Best regards,
--
--- Artur Pietruk, arturp(at)plukwa(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Sullivan | 2002-08-06 21:49:40 | Re: High Availability PostgreSQL HOWTO article |
Previous Message | Robert M. Meyer | 2002-08-06 19:42:19 | Re: High Availability PostgreSQL HOWTO article |