Horton
Menu

Re: Problem with OpenSCG downloads

Bruce Momjian <bruce@momjian.us>

View thread
From: Bruce Momjian <bruce@momjian.us>
To: Magnus Hagander <magnus@hagander.net>
Cc: Andres Freund <andres@anarazel.de>, Justin Clift <justin@postgresql.org>, PostgreSQL www <pgsql-www@postgresql.org>
Date: 2018-08-17T12:34:28Z
Lists: pgsql-hackers 
On Fri, Aug 17, 2018 at 09:48:26AM +0200, Magnus Hagander wrote:
>     Looking at their website now, does it show they now have the proper
>     binaries?
> 
>             https://www.openscg.com/bigsql/postgresql/installers/
> 
>             PostgreSQL 10.5 - Stable  (09-Aug-18)
> 
>                 postgresql-10.5-win64.exe
>                 postgresql-10.5-osx64.dmg
> 
> Per the filenames it looks like they do. But the dates are still backdated on
> them?

Uh, what's the matter with the dates now?  2018-08-09 is the release
date of 10.5.

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

+ As you are, so once was I.  As I am, so you will be. +
+                      Ancient Roman grave inscription +

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Remove test for VA_ARGS, implied by C99.

  2. Introduce minimal C99 usage to verify compiler support.

  3. Require C99 (and thus MSCV 2013 upwards).

  4. Require a C99-compliant snprintf(), and remove related workarounds.

  5. Try to enable C99 in configure, but do not rely on it (yet).

  6. Make snprintf.c follow the C99 standard for snprintf's result value.

  7. Clean up assorted misuses of snprintf()'s result value.