From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Re: [COMMITTERS] pgsql: Perform only one ReadControlFile() during startup. |
Date: | 2017-09-18 18:04:39 |
Message-ID: | 20170918180439.mgxvnbmxzb6br57t@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On 2017-09-18 12:16:42 -0400, Robert Haas wrote:
> On Mon, Sep 18, 2017 at 6:32 AM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> > One thing that I've noticed for a while, but that I was reminded of
> > again here. We very frequently allow psql to reconnect in case of crash,
> > just for postmaster to notice a child has gone and kill that session. I
> > don't recall that frequently happening, but these days it happens nearly
> > every time.
>
> I don't understand what you're talking about here.
I often see a backend crash, psql reacting to that crash by
reconnecting, successfully establish a new connection, just to be kicked
off by postmaster that does the crash restart cycle. I've not yet
figured out when exactly this happens and when not.
- Andres
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2017-09-18 19:21:35 | pgsql: Make DatumGetFoo/PG_GETARG_FOO/PG_RETURN_FOO macro names more co |
Previous Message | Simon Riggs | 2017-09-18 16:55:20 | Re: Re: [COMMITTERS] pgsql: Perform only one ReadControlFile() during startup. |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2017-09-18 19:26:36 | Re: PG_GETARG_GISTENTRY? |
Previous Message | Pavel Stehule | 2017-09-18 17:59:48 | Re: psql: new help related to variables are not too readable |