Thank you, that is good information. The SSL performance issue is
important and I didn't even know to ask about it. Thanks also to Ryan.
On Fri, Jan 2, 2015 at 12:12 AM, Neil Van Dyke wrote:
> Thomas Lynch wrote on 01/01/2015 10:32 AM:
>
>>
>> I don't know if there is an issue that caused the
Thomas Lynch wrote on 01/01/2015 10:32 AM:
I don't know if there is an issue that caused the package to be
distributed with these config settings so I will go with the #:socket
`guess approach until I have a better understanding.
The Debian default settings for PG access are OK to start with
So yes, the Unix socket and TCP local connection are different in the
config file, one being peer, the other being 'md5'
I assume setting the tcp socket to peer in the pg_hba.conf file would work.
I just tested your suggestion of "adding `#:socket 'guess` to your
`postgresql-connect` call" and
On Thu, Jan 1, 2015 at 6:25 PM, Neil Van Dyke wrote:
> Thomas Lynch wrote on 01/01/2015 03:30 AM:
>
>> I am having difficulty connecting to the postgres server from Racket. It
>> asks for a password, but role and authentication is set up so that the
>> logged in local user does not need one.
>>
Thomas Lynch wrote on 01/01/2015 03:30 AM:
I am having difficulty connecting to the postgres server from Racket.
It asks for a password, but role and authentication is set up so that
the logged in local user does not need one.
Is `psql` is using a Unix domain socket to talk to PG,
`postgre
I am having difficulty connecting to the postgres server from Racket. It
asks for a password, but role and authentication is set up so that the
logged in local user does not need one.
1. these versions:
(Debian 4.6.3-14)
Racket 5.2.1
postgres (9.1.14)
2. running psql from a shell prompt doesn'
6 matches
Mail list logo
