| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Thomas Kellerer <shammat(at)gmx(dot)net>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Is this a bug in pg_current_logfile() on Windows? |
| Date: | 2020-07-08 13:45:12 |
| Message-ID: | 4c926ea1-f0f9-b0fa-cbb7-fe67ce18dbeb@aklaver.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On 7/8/20 6:05 AM, Thomas Kellerer wrote:
> Hello,
>
> I noticed the following strage output when running Postgres 12.3 (not psql) on Windows
>
> postgres=# select pg_current_logfile();
> pg_current_logfile
> ------------------------------------
> pg_log/postgresql-2020-07-08.log\r
> (1 row)
>
> Note the "\r" at the end of the file name.
>
> This does not happen when running Postgres on Linux.
>
> Is this intended for some strange reason?
> Or a bug or a technical limitation?
I'm guessing the difference between Unix line ending:
\n
and Windows:
\r\n
>
> Regards
> Thomas
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Yorwerth, Adam | 2020-07-08 14:09:22 | BigSerial and txid issuance |
| Previous Message | Thomas Kellerer | 2020-07-08 13:05:25 | Is this a bug in pg_current_logfile() on Windows? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rémi Lapeyre | 2020-07-08 13:51:28 | Re: [PATCH v2] Allow COPY "text" to output a header and add header matching mode to COPY FROM |
| Previous Message | Robert Haas | 2020-07-08 13:26:16 | Re: Multi-byte character case-folding |