aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/adt/numeric.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2020-01-04 21:33:34 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2020-01-04 21:33:34 -0500
commit48e03583cd373ce67827f4d8a99dcef8242364b0 (patch)
treeb8e2af368fceedf4da59955688ca4d32f8f86be4 /src/backend/utils/adt/numeric.c
parent7e42478186aa8b41a8706f3f53b44e25a427bde9 (diff)
downloadpostgresql-48e03583cd373ce67827f4d8a99dcef8242364b0.tar.gz
postgresql-48e03583cd373ce67827f4d8a99dcef8242364b0.zip
Avoid reading ~/.inputrc in tab-completion test, and revert other changes.
The true explanation for Peter Geoghegan's trouble report turns out to be that he has a ~/.inputrc that affects readline's behavior enough to break this test. Prevent readline from reading that file. Also, the best way to prevent TERM from affecting the results seems to be to unset it altogether, not to set it to "xterm". The latter choice licenses readline to emit xterm escape sequences, and there's a lot of variation in exactly what it will emit. Revert changes that attempted to account exactly for xterm escape sequences. We shouldn't need that with TERM unset, and it was not looking like a maintainable solution anyway. Discussion: https://postgr.es/m/23181.1578167938@sss.pgh.pa.us
Diffstat (limited to 'src/backend/utils/adt/numeric.c')
0 files changed, 0 insertions, 0 deletions