| From: | Thomas Kellerer <shammat(at)gmx(dot)net> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Is this a bug in pg_current_logfile() on Windows? |
| Date: | 2020-07-08 13:05:25 |
| Message-ID: | 412ae8da-76bb-640f-039a-f3513499e53d@gmx.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
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?
Regards
Thomas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2020-07-08 13:45:12 | Re: Is this a bug in pg_current_logfile() on Windows? |
| Previous Message | Shaozhong SHI | 2020-07-08 11:41:19 | Re: create batch script to import into postgres tables |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2020-07-08 13:12:33 | Re: Creating a function for exposing memory usage of backend process |
| Previous Message | Michael Paquier | 2020-07-08 13:00:47 | Re: Towards easier AMs: Cleaning up inappropriate use of name "relkind" |