Hi,
Thanks to all who responded. Right now I'm partial to using the PGPASSWORD
variable. I was so hung up on looking at the applications I forgot about the
underlying libraries.
I can set the environmental variable in the backup script and make that only
readable by root. It looks like someone would need to be root to look at the
environment of a process they don't own, at least on Linux, which is what I'm
running on. If an attacker has root on the box, it's game over anyway, and
this looks safest from a network based attack.
Thanks again,
Darren McClelland
On Tuesday 06 August 2002 11:14, Darren McClelland wrote:
> Hello,
>
> I would like to backup a set of databases from a cron job. It looks like
> pg_dumpall will do the trick. The only problem is that there doesn't seem
> to be any way to pass the database password to pg_dumpall in a non
> interactive manner. I'd like to use some kind of access control on the
> databases, but it would need to be able to function non interactively.
>
> Ideally whatever I do would be able to function across a network, so that
> one database server could backup to a second - kind of a poor man's
> replication.
>
> I haven't found any real answers in any of the archives, or docs. Has
> anyone here done something like this or have any thoughts?
>
> Thanks,
> Darren McClelland
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
