Bruce Momjian wrote:
postgresbugs wrote:
Oliver Jowett wrote:
postgresbugs wrote:
The functionality provided by PGPASSWORD should not be removed unless
there is a functionality other than .pgpass, which is fine for some
uses and not for
Oliver Jowett wrote:
postgresbugs wrote:
Tom Lane wrote:
The point here is that if
PGPASSWORD is passed down to psql as an environmental variable, it is
visible as part of psql's environment for the entire run of psql.
Whatever the calling script does later doesn't remove that
Tom Lane wrote:
Agreed, which is why we invented .pgpass. But that argument scales up
to beyond one invocation of this hypothetical script, does it not?
regards, tom lane
I guarantee you that his process which includes binaries and scripts is
not hypothetical.
Regards,
John Griffiths
Tom Lane wrote:
postgresbugs <[EMAIL PROTECTED]> writes:
Unless the utilities like psql and pg_dump are changed to accept a
password as a command line option, I don't think PGPASSWORD should go
away. It is too useful for those that know how to properly use a
Oliver Jowett wrote:
Tom Lane wrote:
Oliver Jowett <[EMAIL PROTECTED]> writes:
Assuming that you can't tweak .pgpass (for example, you're just
propagating a password you interactively got from the user), what's
the recommended way to provide the password?
In the connection string given to PQconn
I know this is not a bug, but I didn't see a list that I thought this
would fit into.
I saw in the documentation that PGPASSWORD is deprecated in favor of of
the .pgpass file for security reasons.
I would like to recommend removing the deprecation flag from PGPASSWORD.
It is very useful in dyn
Stephan Szabo wrote:
On Thu, 2 Dec 2004, postgresbugs wrote:
On Wed, 1 Dec 2004, Stephan Szabo wrote:
On Wed, 1 Dec 2004, postgresbugs wrote:
> Foreign keys referencing parent table fails on insert if the key is in
the table that inherits the parent ta
On Wed, 1 Dec 2004, Stephan Szabo wrote:
On Wed, 1 Dec 2004, postgresbugs wrote:
> Foreign keys referencing parent table fails on insert if the key is in
> the table that inherits the parent table.
Unfortunately, primary keys, unique constraints and foreign keys
Foreign keys referencing parent table fails on insert if the key is in
the table that inherits the parent table.
I am using psql (PostgreSQL) 7.4.2. I have created a trivial case for an
example.
create table trivial1 (id numeric primary key, numval numeric);
create table trivial2 (textval text)
