On Fri, Jun 16, 2017 at 1:01 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > (2) My inclination would be not to back-patch. This change could break > configurations that worked before, and the lack of prior complaints > says that not many people are having a problem with it.
That's fourteen years without complains, still I cannot imagine any cases where it would be a problem as people who would have faced this problem but not reported it have likely just enforced the FS to handle case-insensitivity for paths. Or they just relied on the default: on Windows the default is to be case-insensitive, as much as OSX. So the proposed patch handles things better with case-sensitive paths, without really impacting users with case-insensive FS. I see the point of not back-patching the change though. -- Michael -- Sent via pgsql-hackers mailing list (firstname.lastname@example.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers