| From: | Thomas Kellerer <shammat(at)gmx(dot)net> |
|---|---|
| To: | Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Is this a bug in pg_current_logfile() on Windows? |
| Date: | 2020-07-08 17:07:20 |
| Message-ID: | bb8f2c7f-2bee-35bd-d57e-62864e95bb89@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Tom Lane schrieb am 08.07.2020 um 18:41:
> Somehow, the reading file is being left in binary mode and thus it's
> failing to convert \r\n back to plain \n.
>
> Now the weird thing about that is I'd have expected "r" and "w" modes
> to imply Windows text mode already, so that I'd have figured that
> _setmode call to be a useless no-op. Apparently on some Windows libc
> implementations, it's not. How was your installation built exactly?
That's the build from EnterpriseDB
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Luiz Hugo Ronqui | 2020-07-08 19:27:47 | pg_dump / pg_restore option |
| Previous Message | Tom Lane | 2020-07-08 16:43:59 | Re: PostgreSQL 12 - ERROR: could not rename file "pg_logical/snapshots/1A-7C00D890.snap.13594.tmp" to "pg_logical/snapshots/1A-7C00D890.snap": No space left on device |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2020-07-08 17:18:00 | Re: TAP tests and symlinks on Windows |
| Previous Message | Andres Freund | 2020-07-08 17:03:48 | Re: Creating a function for exposing memory usage of backend process |