From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
---|---|
To: | Juan José Santamaría Flecha <juanjo(dot)santamaria(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: WIN32 pg_import_system_collations |
Date: | 2021-12-14 21:45:28 |
Message-ID: | CA+hUKGKHu5M9CzD+oueMfW6pr9g9koLaYio=b57QRjrFd1++zQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Dec 15, 2021 at 9:14 AM Juan José Santamaría Flecha
<juanjo(dot)santamaria(at)gmail(dot)com> wrote:
> What I meant to say is that to run the test, you need a database that has successfully run pg_import_system_collations. This would be also possible in Mingw for _WIN32_WINNT> = 0x0600, but the current value in src\include\port\win32.h is _WIN32_WINNT = 0x0501 when compiling with Mingw.
Ah, right. I hope we can make the leap to 0x0A00 (Win10) soon and
just stop thinking about these old ghosts, as mentioned by various
people in various threads. Do you happen to know if there are
complications for that, with the non-MSVC tool chains?
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2021-12-14 22:12:44 | Re: Synchronizing slots from primary to standby |
Previous Message | Tomas Vondra | 2021-12-14 21:28:11 | Re: Column Filtering in Logical Replication |