diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2020-10-28 14:35:53 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2020-10-28 14:35:53 -0400 |
| commit | cb0982ba9796e16a0d38953c14ef32af657e6fd4 (patch) | |
| tree | edb11ce2270327ec14adc669439ab7160e9c16f4 /src/backend/executor/nodeModifyTable.c | |
| parent | 43330cdd40f12f352bc8f8100974c4b7eeb45d18 (diff) | |
| download | postgresql-cb0982ba9796e16a0d38953c14ef32af657e6fd4.tar.gz postgresql-cb0982ba9796e16a0d38953c14ef32af657e6fd4.zip | |
Use mode "r" for popen() in psql's evaluate_backtick().
In almost all other places, we use plain "r" or "w" mode in popen()
calls (the exceptions being for COPY data). This one has been
overlooked (possibly because it's buried in a ".l" flex file?),
but it's using PG_BINARY_R.
Kensuke Okamura complained in bug #16688 that we fail to strip \r
when stripping the trailing newline from a backtick result string.
That's true enough, but we'd also fail to convert embedded \r\n
cleanly, which also seems undesirable. Fixing the popen() mode
seems like the best way to deal with this.
It's been like this for a long time, so back-patch to all supported
branches.
Discussion: https://postgr.es/m/16688-c649c7b69cd7e6f8@postgresql.org
Diffstat (limited to 'src/backend/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions