Re: pgsql: Allow concurrent-safe open() and fopen() in frontend code for Wi
От | Tom Lane |
---|---|
Тема | Re: pgsql: Allow concurrent-safe open() and fopen() in frontend code for Wi |
Дата | |
Msg-id | 26882.1537372501@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: pgsql: Allow concurrent-safe open() and fopen() in frontend codefor Wi (Michael Paquier <michael@paquier.xyz>) |
Ответы |
Re: pgsql: Allow concurrent-safe open() and fopen() in frontend codefor Wi
|
Список | pgsql-hackers |
Michael Paquier <michael@paquier.xyz> writes: > I have spent a large portion of my morning trying to test all the > solutions proposed, and a winner shows up. ... > - win32-open-laurenz.patch, which enforces to text mode only if binary > mode is not defined, which maps strictly to what pre-11 is doing when > calling the system _open or _fopen. And surprisingly, this is proving > to pass all the tests I ran: bincheck (including pgbench and pg_dump), > upgradecheck, recoverycheck, check, etc. initdb --pwfile is not > complaining to me either. I'm OK with this approach. I wonder though what happens if you take away the "#ifdef FRONTEND" and just enforce that one or the other mode is selected always. That would seem like a sensible solution rather than a wart to me ... regards, tom lane
В списке pgsql-hackers по дате отправления: