From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | pgsql: Enforce translation mode for Windows frontends to text with open |
Date: | 2018-09-19 23:56:42 |
Message-ID: | E1g2mKo-0005Zx-5e@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Enforce translation mode for Windows frontends to text with open/fopen
Allowing frontends to use concurrent-safe open() and fopen() via 0ba06e0
has the side-effect of switching the default translation mode from text
to binary, so the switch can cause breakages for frontend tools when the
caller of those new versions specifies neither binary and text. This
commit makes sure to maintain strict compatibility with past versions,
so as no frontends should see a difference when upgrading.
Author: Laurenz Albe
Reviewed-by: Michael Paquier, Tom Lane
Discussion: https://postgr.es/m/20180917140202.GF31460@paquier.xyz
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/40cfe86068f4c385517a8423cb8b3001e2f6a2fd
Modified Files
--------------
src/port/open.c | 14 ++++++++++++++
1 file changed, 14 insertions(+)
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2018-09-19 23:58:20 | Re: pgsql: Allow concurrent-safe open() and fopen() in frontend code for Wi |
Previous Message | Tom Lane | 2018-09-19 21:07:04 | pgsql: Fix minor error message style guide violation. |