aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/adt/numeric.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2016-01-04 20:08:08 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2016-01-04 20:08:08 -0500
commit9b181b0363deb65b15a9feaf3eb74f86707498a9 (patch)
treed5134d67a3af64381bb4978be2e3e57a93f8a7b0 /src/backend/utils/adt/numeric.c
parent7debf36072b3a088b3003aab6dcf57c3f186100d (diff)
downloadpostgresql-9b181b0363deb65b15a9feaf3eb74f86707498a9.tar.gz
postgresql-9b181b0363deb65b15a9feaf3eb74f86707498a9.zip
In psql's tab completion, change most TailMatches patterns to Matches.
In the refactoring in commit d37b816dc9e8f976c8913296781e08cbd45c5af1, we mostly kept to the original design whereby only the last few words on the line were matched to identify a completable pattern. However, after commit d854118c8df8c413d069f7e88bb01b9e18e4c8ed, there's really no reason to do it like that: where it's sensible, we can use patterns that expect to match the entire input line. And mostly, it's sensible. Matching the entire line greatly reduces the odds of a false match that leads to offering irrelevant completions. Moreover (though I've not tried to measure this), it should make tab completion faster since many of the patterns will be discarded after a single integer comparison that finds that the wrong number of words appear on the line. There are certain identifiable places where we still need to use TailMatches because the statement in question is allowed to appear embedded in a larger statement. These are just a small minority of the existing patterns, though, so the benefit of switching where possible is large. It's possible that this patch has removed some within-line matching behaviors that are in fact desirable, but we can put those back when we get complaints. Most of the removed behaviors are certainly silly. Michael Paquier, with some further adjustments by me
Diffstat (limited to 'src/backend/utils/adt/numeric.c')
0 files changed, 0 insertions, 0 deletions