Robert Haas <robertmh...@gmail.com> writes:
> The level of effort you've put into this is extremely impressive, but
> I can't shake the feeling that you're going to keep finding issues in
> the test setup, the operating system, or the upstream libraries,
> rather than bugs in PostgreSQL. Maybe this is all just one-time
> stabilization effort, but...
Yeah, this is pretty nearly what I feared would happen, given libedit's
apparently-well-earned evil reputation. I suspect that the filename
completion tests I posted over in that thread may expose another round
of issues. If we can get past that, I think that expanding our test
coverage for the rest of tab-complete.c should be relatively
unproblematic, because there aren't very many other readline behaviors
that tab-complete.c is depending on.
One alternative is to give up on the idea of ever having any test
coverage for tab-complete.c, which doesn't seem very desirable.
Or we could disable the tests when using libedit, or provide some
switch to make it easier for the user/packager to do so.
In Debian's case, I suspect that they don't care about the behavior
when using libedit, so skipping the test would be just fine for them.
What they really ought to test is what happens after they sub in
libreadline at runtime ... but I imagine that their dubious legal
theories about all this would prevent them from actually doing that
during the package build.
regards, tom lane
PS: Stepping back from the immediate problem, it's obviously better
for all concerned if libedit is usable with Postgres. So if they're
willing to patch problems, which we've found out they are, then coping
with this stuff is a win in the long run.
