Re: Is this a bug in pg_current_logfile() on Windows? - Mailing list pgsql-general

From Thomas Kellerer
Subject Re: Is this a bug in pg_current_logfile() on Windows?
Date
Msg-id bb8f2c7f-2bee-35bd-d57e-62864e95bb89@gmx.net
Whole thread Raw
In response to Re: Is this a bug in pg_current_logfile() on Windows?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
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

https://www.enterprisedb.com/download-postgresql-binaries





pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: 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
Next
From: "Luiz Hugo Ronqui"
Date:
Subject: pg_dump / pg_restore option