Re: postgres_fdw hint messages
Nathan Bossart <nathandbossart@gmail.com>
From: Nathan Bossart <nathandbossart@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Robert Haas <robertmhaas@gmail.com>, Peter Eisentraut <peter.eisentraut@enterprisedb.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2022-09-02T21:26:09Z
Lists: pgsql-hackers
Attachments
On Thu, Sep 01, 2022 at 04:31:20PM -0700, Nathan Bossart wrote: > On Thu, Sep 01, 2022 at 07:08:49PM -0400, Tom Lane wrote: >> (1) there probably needs to be some threshold of closeness, so we don't >> offer "foobar" when the user wrote "huh" > > Agreed. > >> (2) there are several places doing this now, and there will no doubt >> be more later, so we need to try to abstract the logic so it can be >> shared. > > Will do. Here is a new patch. Two notes: * I considered whether to try to unite this new functionality with the existing stuff in parse_relation.c, but the existing code looked a bit too specialized. * I chose a Levenshtein distance of 5 as the threshold of closeness for the hint messages. This felt lenient, but it should hopefully still filter out some of the more ridiculous suggestions. However, it's still little more than a wild guess, so if folks think the threshold needs to be higher or lower, I'd readily change it. -- Nathan Bossart Amazon Web Services: https://aws.amazon.com
Commits
-
postgres_fdw: Remove useless DO block in test
- 32b507378fac 16.0 landed
-
Adjust assorted hint messages that list all valid options.
- 5ac51c8c9e44 16.0 landed