From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com> |
Cc: | <pgsql-hackers(at)postgresql(dot)org>, <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: Compile failure with SSL |
Date: | 2004-06-22 07:30:53 |
Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E40C366F@ratbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
> -----Original Message-----
> From: Merlin Moncure [mailto:merlin(dot)moncure(at)rcsonline(dot)com]
> Sent: 21 June 2004 15:40
> To: Dave Page
> Cc: pgsql-hackers(at)postgresql(dot)org; pgsql-patches(at)postgresql(dot)org
> Subject: RE: [HACKERS] Compile failure with SSL
>
> I had made the same changes as you to be_secure...(actually,
> I recently stopped doing that, I need to update the snapshot
> info page). The real problem is that the SSL based
> connection does not receive signals while waiting on select()
> like the regular connection does. IMO, the SSL patch should
> not be applied until this has been resolved.
Urrgghh - no ssl support on Windows :-(. I assume this is not a trivial
thing to fix?
I'm not sure I agree with leaving the patch off though - leaving the
code intentionally broken is not a nice way to disable an unsupported
feature, especially when the patch has nothing to do with the reasons
for not including said feature.
Regards, Dave
From | Date | Subject | |
---|---|---|---|
Next Message | Kreißl, Karsten | 2004-06-22 09:50:22 | User Privileges using dblink |
Previous Message | Shachar Shemesh | 2004-06-22 07:19:35 | Re: Casts question |
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2004-06-23 00:32:48 | Re: nested xacts and phantom Xids |
Previous Message | Tom Lane | 2004-06-22 04:42:30 | Re: nested xacts and phantom Xids |