Re: pg_dump "feature"

Thanks for the answer[s].
Interesting that when i launch the command from php through exec() it works
fine even on pg_dump 7.3.x
I guess this feature works only on [shell] command line.

This is the php code:

$tmp_fname = tempnam("/tmp", "file-");
$f = fopen($tmp_fname, "w");
fwrite($f, "$username\n".USER_DB_PASSWORD."\n");
fclose($f);

$cmd = "pg_dump $add_cmd $export $add_table < $tmp_fname";
$result = system($cmd);
unlink($tmp_fname);

----- Original Message -----
From: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Viorel Dragomir" <bc(at)vio(dot)ro>
Cc: <pgsql-sql(at)postgresql(dot)org>
Sent: Wednesday, July 16, 2003 5:29 PM
Subject: Re: [SQL] pg_dump "feature"

> "Viorel Dragomir" <bc(at)vio(dot)ro> writes:
> > In 7.3.x the pg_dump accepts the password only from stdin. The user must
en=
> > ter his password.
> > It's a feature or a bug, because i can't see any logic in this
behaviour.
>
> It's a feature ... or at least an intentional change.
>
> If you want to keep your password in a file, see the ~/.pgpass feature.
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
> joining column's datatypes do not match