"David G. Johnston" <david.g.johnston@gmail.com> writes:
>> The following bug has been logged on the website:
>> (4) press up arrow key to try to execute the previous SQL of the step(2)
>> again
>> (5) Occasionally, it will show you nothing about the SQL, then you can try
>> to input a character ';' and press Enter key, the PostgreSQL will crash
>> unexpectedly
> It would help to explain what you actually see in step 5 instead of just
> saying crash. In particular is the "failure" in the server or client?
I'd lay long odds that what's being described is a psql crash not a
server crash, and furthermore that the problem is in libreadline
(which is what would be handling up-arrow response). We've heard
reports before of flaky readline behavior on Windows. I failed to
find an exact match to this report in a moment's worth of trawling
the archives, though I did find for instance
https://www.postgresql.org/message-id/flat/6a2534f3-4359-617d-d314-17174454eb6d%40orange.fr
I think the questions to ask are around where did this copy of
psql.exe come from, and what version of readline is included in
it, and whether that's up-to-date.
regards, tom lane
