Hi, Le mardi 07 novembre 2017, Amir Goldstein a écrit : > > FWIW, in my failing case, it uses PostgreSQL 10.0 as in Debian > > Testing/Unstable. In Ubuntu, it's only available in Bionic Beaver (development > > release). > > And is this the same PostgreSQL version that worked with kernel v4.12.6? No. Postgresql 10 became the default in Debian Testing on October 11th and we switched to Linux 3.13.4 on October 9th, so at about the same time... And it seems likely that this fsync() call has been added as part of PostgreSQL 10 in that commit: https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=1b02be21f271db6bd3cd43abb23fa596fcb6bac3 > Perhaps this a PostgreSQL regression (when storing db on overlayfs/squashfs) > that should be reported to PostgreSQL developers? I will do that in parallel but it seems awkward to have a writable filesystem where fsync() is not working... I can understand the desire to delegate to the underlying filesystem but that's one more case where we might want to hide the fact that we have a read-only layer below. Cheers, -- Raphaël Hertzog ◈ Writer/Consultant ◈ Debian Developer Discover the Debian Administrator's Handbook: → https://debian-handbook.info/get/ -- To unsubscribe from this list: send the line "unsubscribe linux-unionfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
