Re: PQinitSSL broken in some use casesf

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Merlin Moncure <mmoncure(at)gmail(dot)com>, Andrew Chernow <ac(at)esilo(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PQinitSSL broken in some use casesf
Date: 2009-02-13 21:53:31
Message-ID: 603c8f070902131353p672636d0ldc7e16fe926cdf12@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> BTW, the bitmask isn't perfect either --- doesn't it just reintroduce
> the problem already complained of with your idea for PQinitSSL? That
> is, how does the client know whether the function recognized all the
> bits it passed?

Well, if we add the PQgetLibraryVersion() function I suggested
upthread, then it can check that first. I find it difficult to
believe that isn't a good idea independently of how we solve this
particular problem.

...Robert

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-02-13 21:54:50 Re: [patch] fix for regression tests (locale cs_CZ)
Previous Message Andrew Chernow 2009-02-13 21:32:15 Re: PQinitSSL broken in some use casesf