From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | "mzhao(at)insight-tec(dot)co(dot)jp" <mzhao(at)insight-tec(dot)co(dot)jp>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: BUG #15076: postmaster crashes unexpectedly when using up arrow key in psql command |
Date: | 2018-02-22 03:29:00 |
Message-ID: | CAKFQuwa9r_P+zminmPFJAs2nydDAmTD8Dvzx4EUcUpdQE_-Lgg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
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.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2018-02-22 04:06:49 | Re: BUG #15076: postmaster crashes unexpectedly when using up arrow key in psql command |
Previous Message | 石勇虎 | 2018-02-22 02:38:22 | 答复: response time is very long in PG9.5.5 using psql or jdbc |