Harald Armin Massa wrote:
Hello,
in the release notes there is a "FAT is not really supported" notice
for PostgreSQL.
I suggest following workaround:
create a cacls.exe and put it first in the search path. That cacls.exe
should just return "OK" no matter of the imput-params.
Be warned that "FAT is not really supported" has good reasons.
I think that we have to decide if postgres is supposed to work on
FAT32 or not. If, as I expect, the response is not, then we have to find
a relaiable way to detect a NTFS ( also when a tablespace is created BTW )
and refuse to start on a FATXX, and not trust on the failre of a cacls.exe
My 2 cents.
Regards
Gaetano Mendola
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
