Re: [HACKERS] Re: [COMMITTERS] pgsql: Perform only oneReadControlFile() during startup.
От | Andres Freund |
---|---|
Тема | Re: [HACKERS] Re: [COMMITTERS] pgsql: Perform only oneReadControlFile() during startup. |
Дата | |
Msg-id | 20170918180439.mgxvnbmxzb6br57t@alap3.anarazel.de обсуждение исходный текст |
Ответ на | Re: [HACKERS] Re: [COMMITTERS] pgsql: Perform only oneReadControlFile() during startup. (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: [HACKERS] Re: [COMMITTERS] pgsql: Perform only one ReadControlFile() during startup.
Re: [HACKERS] Re: [COMMITTERS] pgsql: Perform only oneReadControlFile() during startup. |
Список | 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@anarazel.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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
В списке pgsql-hackers по дате отправления: