Hi,
On Sun, 2018-04-01 at 18:07 -0400, Tom Lane wrote:
> 4. Move our minimum supported Python version up to 2.6 (from 2.4
> where it is now).
>
> #4 seems like an overreaction at first sight, but on the other
> hand, I wonder how many people really care about pre-2.6 anymore
> anyway. (2.4 was
I wrote:
> gaur (python 2.5) is showing a different output pathology:
A bit of google research indicates that Python did not have reliable
handling of infinity or NaN floats until 2.6; before that, you could
get failures or platform-specific results from code like float('inf').
So this test ain't
Fix a boatload of typos in C comments.
Justin Pryzby
Discussion: https://postgr.es/m/20180331105640.gk28...@telsasoft.com
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/0b11a674fb11cc1571326c861ecdd7773d9e587f
Modified Files
--
contrib/pgcrypto/rijnda
On Sat, Mar 31, 2018 at 9:52 AM, Tom Lane wrote:
> Portability fix for commit 9a895462d.
>
> So far as I can find, NI_MAXHOST isn't actually required anywhere by
> POSIX. Nonetheless, commit 9a895462d supposed that it could rely on
> having that symbol without any ceremony at all. We do have a h
Michael Paquier writes:
> I have not check in details this thread so I may be saying something
> stupid... But if you are looking for a frontend implementation for
> strong randoms, please extract pg_frontend_random in fe-auth-scram.c and
> move it to its own file for example in src/common as a f
On Sat, Mar 31, 2018 at 07:43:38PM +0200, Fabien COELHO wrote:
> Indeed, I clearly misunderstood its usage pattern. I looked at its source
> ("src/port/pg_strong_random.c") where the function is always defined and is
> documented as returning false if it does not find a strong random source, so
> I
