Re: Can't connect to Windows port + other
От | Anony Mous |
---|---|
Тема | Re: Can't connect to Windows port + other |
Дата | |
Msg-id | 015101c4907e$f2fa8580$6a02a8c0@PETER обсуждение исходный текст |
Ответ на | Re: Can't connect to Windows port + other (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Can't connect to Windows port + other
|
Список | pgsql-general |
Great, I found the part of the docs referring to this (ch 27.11) however, it refers to creating this file in the user's home directory. It seems this part of the documentation is assuming I'm using *nix. In Windows, where should this file be located? Also, .pgpass is an invalid file name in Win. Thanks! -----Original Message----- From: Tom Lane [mailto:tgl@sss.pgh.pa.us] Sent: September 1, 2004 5:19 PM To: Anony Mous Cc: pgsql-general@postgresql.org Subject: Re: [GENERAL] Can't connect to Windows port + other "Anony Mous" <A.Mous@shaw.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
В списке pgsql-general по дате отправления: