Message-ID: <00be01c34ba8$aec682e0$0600a8c0@fix.ro>
From: "Viorel Dragomir" <bc@vio.ro>
To: <pgsql-sql@postgresql.org>
References: <004501c34b9f$f7d8f520$0600a8c0@fix.ro>
	<18025.1058365770@sss.pgh.pa.us>
Subject: Re: pg_dump "feature" 
Date: Wed, 16 Jul 2003 17:43:54 +0300
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-2"
Content-Transfer-Encoding: 7bit

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@sss.pgh.pa.us>
To: "Viorel Dragomir" <bc@vio.ro>
Cc: <pgsql-sql@postgresql.org>
Sent: Wednesday, July 16, 2003 5:29 PM
Subject: Re: [SQL] pg_dump "feature"


> "Viorel Dragomir" <bc@vio.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