Re: BUG #16688: psql removes only LF without CR at end of backquotes on windows.
От | Tom Lane |
---|---|
Тема | Re: BUG #16688: psql removes only LF without CR at end of backquotes on windows. |
Дата | |
Msg-id | 1441558.1603910379@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: BUG #16688: psql removes only LF without CR at end of backquotes on windows. (Bruce Momjian <bruce@momjian.us>) |
Ответы |
Re: BUG #16688: psql removes only LF without CR at end of backquotes on windows.
|
Список | pgsql-bugs |
Bruce Momjian <bruce@momjian.us> writes: > On Tue, Oct 27, 2020 at 11:27:05PM -0400, Tom Lane wrote: >> But rather than mess with that newline-chomping code, I'm >> inclined to wonder why we're using PG_BINARY_R for input >> that we clearly expect to be textual. Most of our other >> popen's do not do that. >> >> Bruce, this seems to date to 98e9775a3 ... don't suppose >> you remember that? I see the point about control-Z in text >> files, but I wonder how plausible that is for popen cases. > It seems safe for popen to use TEXT mode, and it might help with > encoding conversion. I don't think I made a popen distinction when I > was working in this area. I double-checked, and verified that our only other popen() calls that use binary mode are dealing with COPY data. It seems appropriate to do so in that case, partly because the data might indeed be binary and partly because we have adequate newline recognition logic in copy.c. But it does seem best to uniformly use plain "r" or "w" for other popen's. So I've fixed this that way. regards, tom lane
В списке pgsql-bugs по дате отправления: