diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2022-02-02 23:01:56 -0500 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2022-02-02 23:01:56 -0500 |
| commit | 4b0e37faaf5ffe1552a07438323341c6394890da (patch) | |
| tree | c24069feb0ccbda5de592cf292e27cfd07e0e01f /src/backend/parser/parse_utilcmd.c | |
| parent | 9d179d9c23b9d4cc1a4ffa02e4de79114de064d7 (diff) | |
| download | postgresql-4b0e37faaf5ffe1552a07438323341c6394890da.tar.gz postgresql-4b0e37faaf5ffe1552a07438323341c6394890da.zip | |
Remove configure's check for rl_completion_append_character.
The comment for PGAC_READLINE_VARIABLES says "Readline versions < 2.1
don't have rl_completion_append_character". It seems certain that such
versions are extinct in the wild, though; for sure there are none in the
buildfarm. Libedit has had this variable for at least twenty years too.
Also, tab-complete.c's behavior without it is quite unfriendly, since
we'll emit a space even when completion fails; but we've had no
complaints about that.
Therefore, let's assume this variable is always there, and drop the
configure check to save a few build cycles.
Discussion: https://postgr.es/m/147685.1643858911@sss.pgh.pa.us
Diffstat (limited to 'src/backend/parser/parse_utilcmd.c')
0 files changed, 0 insertions, 0 deletions