Re: Loaded footgun open_datasync on Windows
Laurenz Albe <laurenz.albe@cybertec.at>
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Noah Misch <noah@leadboat.com>
Cc: Michael Paquier <michael@paquier.xyz>, Kuntal Ghosh <kuntalghosh.2007@gmail.com>, Amit Kapila <amit.kapila16@gmail.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2018-09-10T14:46:40Z
Lists: pgsql-hackers
Attachments
- 0001-Use-pgwin32_open-in-frontend-code-on-Windows_V3.patch (text/x-patch) patch 0001
Noah Misch wrote: > On Wed, Jun 27, 2018 at 12:09:24PM +0200, Laurenz Albe wrote: > > Michael Paquier wrote: > > > > I have added it to the July commitfest. > > > > > > Have you looked at the possibility of removing the log file constraints > > > in pg_upgrade with the change you are doing here so as things would be > > > more consistent with non-Windows platforms, simplifying some code on the > > > way? > > > > Can you explain what the "log file constraints" are? > > If it is in any way related, and I can handle it, sure. > > See this comment in pg_upgrade.h: > > /* > * WIN32 files do not accept writes from multiple processes > * > * On Win32, we can't send both pg_upgrade output and command output to the > * same file because we get the error: "The process cannot access the file > * because it is being used by another process." so send the pg_ctl > * command-line output to a new file, rather than into the server log file. > * Ideally we could use UTILITY_LOG_FILE for this, but some Windows platforms > * keep the pg_ctl output file open by the running postmaster, even after > * pg_ctl exits. > * > * We could use the Windows pgwin32_open() flags to allow shared file > * writes but is unclear how all other tools would use those flags, so > * we just avoid it and log a little differently on Windows; we adjust > * the error message appropriately. > */ > > If you grep src/bin/pg_upgrade for WIN32, roughly a third of the hits are > workarounds for this problem. I agree with Michael that removing those > workarounds would be a good test of frontend pgwin32_open() and worth > including in the initial commit. Thank you for the explanation. I didn't get pg_upgrade to work without the log file hacks; I suspect that there is more than just log file locking going on, but my Windows skills are limited. How shall I proceed? I think that it is important to get pg_test_fsync to work correctly on Windows, and if my patch does not break the buildfarm, that's what it does. I have attached a new version, the previous one was bit-rotted. Yours, Laurenz Albe
Commits
-
Allow concurrent-safe open() and fopen() in frontend code for Windows
- f02259fe93e7 11.0 landed
- 0ba06e0bfb8c 12.0 landed
-
Fix inclusions of c.h from .h files.
- a72f0365db41 10.0 cited
-
Allow borland compiles.
- fd7c3f67e0bc 8.0.0 cited
-
Corrects issues recently posted by Dann Corbit, allowing libpq/psql to
- 422d4819ee7c 8.0.0 cited