Re: BUG #15076: postmaster crashes unexpectedly when using up arrow key in psql command

Hi, Tom,

You mean that the up-arrow key operation in psql.exe may send a SIGINT(or
SIGTERM) signal to server(postmaster) unexpectedly?

Thanks,
Mingchun

-----------------------------------------------------------------------------------
Insight Technology, Inc. Mingchun Zhao, 趙 明春(チョウ メイシュン)
EbisBusinessTower 5F, 1-19-19, Shibuya-ku, Tokyo
TEL : +81-3-5475-1452 FAX : +81-3-5475-1451
Email : mzhao(at)insight-tec(dot)co(dot)jp WWW : http://www.insight-tec.com
-----------------------------------------------------------------------------------

2018-02-22 13:06 GMT+09:00 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:

> "David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)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
>