From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | 趙明春 <mzhao(at)insight-tec(dot)co(dot)jp> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Paquier <michael(at)paquier(dot)xyz>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, "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-24 22:09:41 |
Message-ID: | CABUevEz6H0AHkShhZ0cYO=sUdg+8qwmnt8_S7SMg1FKXhdpHpg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Fri, Feb 23, 2018 at 3:16 AM, 趙明春 <mzhao(at)insight-tec(dot)co(dot)jp> wrote:
> Hi, Tom and Magnus,
>
> Thanks for your information for this issue.
>
> > AFAIC Windows has no way to disassociate a process with a console window
> in a similar way.
>
> Can this be a solution for this issue to add an option
> CREATE_NEW_PROCESS_GROUP to CreateProcess() function into pg_ctl.exe to
> start postgres.exe process?
>
That definitely sounds like it should be worth a try.
> I will say though that most people run the postmaster as a background
> service on Windows, rather than launching it manually.
>
> Unfortunately, we also met this issue, with poor reproducibility, when we
> running the postmaster as Windows Service.
> Maybe this is another story than launching it manually by pg_ctl.exe.
> I will update you if I get any new information.
>
>
That sounds very strange. I'm not saying you're not running into an issue
there, but my guess would be you're actually running into a different
problem (which may have similar symptoms).
//Magnus
From | Date | Subject | |
---|---|---|---|
Next Message | PG Bug reporting form | 2018-02-25 01:08:17 | BUG #15085: Domain "not null" constraint doesn't detect a null returned from a resultset |
Previous Message | Tom Lane | 2018-02-24 20:12:10 | Re: BUG #15080: ecpg on windows doesn't define HAVE_LONG_LONG_INT |