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

​​Hi, david,

> 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?

It looks like the postmaster has received signal 2 in step 5, the following
is the corresponding PostgreSQL log:
==
0000: 2018-02-19 15:37:34 JST [3492]: [65-1] user = ,db = ,remote = app =
DEBUG: postmaster received signal 2
00000: 2018-02-19 15:37:34 JST [3492]: [66-1] user = ,db = ,remote = app
= LOG: received fast shutdown request
00000: 2018-02-19 15:37:34 JST [3492]: [67-1] user = ,db = ,remote = app
= LOG: aborting any active transactions
==

​Regards,
Mingchun​

2018-02-22 12:29 GMT+09:00 David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>:

>
>
> On Wednesday, February 21, 2018, PG Bug reporting form <
> noreply(at)postgresql(dot)org> wrote:
>
>> The following bug has been logged on the website:
>>
>> Bug reference: 15076
>> Logged by: Mingchun Zhao
>> Email address: mzhao(at)insight-tec(dot)co(dot)jp
>> PostgreSQL version: 9.3.20
>> Operating system: Windows
>> Description:
>>
>> steps to reproduce:
>>
>> (1) run psql.exe in a Windows Command Prompt
>> (2) execute a SQL with more than one page of results, e.g. `show all;`
>> (3) press Ctrl + C to break it on the first page
>> (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?
>
> David J.
>