Re: Can't connect to Windows port + other

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Anony Mous" <A(dot)Mous(at)shaw(dot)ca>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Can't connect to Windows port + other
Date: 2004-09-01 23:19:20
Message-ID: 11307.1094080760@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Anony Mous" <A(dot)Mous(at)shaw(dot)ca> writes:
> If so, why not set the listen_addresses to '*' right away?

Security. It was difficult enough to get people to accept the current
liberalized default --- I don't think they'll go for defaulting to -i,
which is essentially what you're asking for. It's seen as a good thing
that there are two, not one, levels of protection between you and having
a database server that's wide open to the entire internet.

> but it always fails because I don't know how to add the password for the
> super user into the command line, and of course the super user will always
> have a password. Is there a way to do this?

Create a .pgpass file maybe?

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Thomas F.O'Connell 2004-09-01 23:19:45 Re: Understanding pg_autovacuum CPU Usage
Previous Message Doug McNaught 2004-09-01 23:12:22 Re: Can't connect to Windows port + other