Re:The dangers of streaming across versions of glibc: A caut...
by leeter on Tuesday January 08, 2019 @12:01PM
(#18857107)
It has always amused me that NTFS and NT Kernel are both case sensitive when it comes to filenames. But WIN32 emulates the case insensitive legacy behavior because people won't fix, or can't fix legacy code. That said applications can properly opt into POSIX semantics.
Re:The dangers of streaming across versions of glibc: A caut...
by voltagex_ on Tuesday January 08, 2019 @07:18PM
(#18861143)
Are you talking about WSL or some other way that applications can use POSIX on Windows?
Re:The dangers of streaming across versions of glibc: A caut...
by blattimwind on Tuesday January 08, 2019 @10:29PM
(#18862025)
FILE_FLAG_POSIX_SEMANTICS
Re:The dangers of streaming across versions of glibc: A caut...
by wrs on Wednesday January 09, 2019 @02:59AM
(#18863094)
IIRC, the NTFS filesystem has its own collation tables on disk that are fixed when the volume is formatted, so its indexes are forever consistent but don’t necessarily match the ongoing changes to collations. Thus the shell has to re-sort everything before showing it, even though you’d think the filenames were already sorted by NTFS.
Of course, PostgreSQL is one the few programs which actually cares about collation and case-insensitivity, so it has to work the hard way.