From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Petr Jelinek <petr(at)2ndquadrant(dot)com>, Christian Ullrich <chris(at)chrullrich(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: VS 2015 support in src/tools/msvc |
Date: | 2016-04-22 03:51:27 |
Message-ID: | 57199FBF.4070706@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 04/21/2016 05:15 PM, Tom Lane wrote:
>
> IIRC, we had intentionally left contrib/seg using mostly V0 calling
> convention as a canary to let us know when that broke. It's a bit
> astonishing that it lasted this long, maybe. But it looks like we're
> going to have to convert at least the bool-returning functions to V1
> if we want it to work on VS 2015.
>
> Do the other contrib modules all pass? I can't recall if seg was the
> only one we'd left like this.
>
>
Only seg fails.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2016-04-22 04:30:56 | Re: VS 2015 support in src/tools/msvc |
Previous Message | Peter Geoghegan | 2016-04-22 03:37:54 | New 9.6 external sort guidance around temp_tablespaces and maintenance_work_mem |