Re: SSL Connection / Windows + Cygwin + PostgreSQL 7.4

From: Barry Lind <blind(at)xythos(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Carlos Guzman Alvarez <carlosga(at)telefonica(dot)net>, Developement <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: SSL Connection / Windows + Cygwin + PostgreSQL 7.4
Date: 2003-08-14 20:01:25
Message-ID: 3F3BEA95.6050209@xythos.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom,

I also see S and N, and do for the database versions I have tested
against (7.2, 7.3 and 7.4). I always thought this was just a doc bug
with the FE/BE protocol docs.

--Barry

Tom Lane wrote:
> Carlos Guzman Alvarez <carlosga(at)telefonica(dot)net> writes:
>
>>Now two questions about SSL Request message:
>
>
>>1. I'm getting as response an 'S' instead of an 'Y' is this ok ??
>
>
> Doesn't sound right. A recent (7.1 or later) postmaster will always
> return 'Y' or 'N'. Older postmasters will not recognize the SSLRequest
> code and will return an 'E' message bleating about bad protocol number.
>
>
>>2. In which format are sent the error messages for an SSL Request ?? (I
>>ask this because i think they are sent in 2.0 format i'm rigth??)
>
>
> Always 2.0, because only a pre-7.1 postmaster will return an error.
> It's not clear to me that you really need to bother to parse the
> message, though. The only thing you can do is close the connection
> and try again non-SSL (or fail if you don't want non-SSL).
>
> 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
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2003-08-14 20:05:10 Re: SSL Connection / Windows + Cygwin + PostgreSQL 7.4 Beta 1 question
Previous Message Tom Lane 2003-08-14 19:15:00 Re: 7.4beta1 build problem on unixware