EXEC_BACKEND + logging_collector=on is broken

Поиск
Список
Период
Сортировка
От Andres Freund
Тема EXEC_BACKEND + logging_collector=on is broken
Дата
Msg-id 20150113182344.GF12272@alap3.anarazel.de
обсуждение исходный текст
Ответы Re: EXEC_BACKEND + logging_collector=on is broken  (Magnus Hagander <magnus@hagander.net>)
Список pgsql-hackers
Hi,

Currently the combination from $subject fails for me with "could not
read from backend variables file ...".

The origin for that problem seems to be b94ce6e80 which moved
RemovePgTempFiles() to after SysLogger_Start(). Unless the syslogger
starts up very quickly RemovePgTempFiles() will have deleted the server
variables file.

I think moving the RemovePgTempFiles() to just above SysLogger_Start()
should preserve the faster reporting for pg_ctl intended by b94ce6e80
and fix the startup issue?

I'm rather surprised that this hasn't caused more problems. Apparently
windows users don't use the logging_collector?

Greetings,

Andres Freund

-- Andres Freund                       http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training &
Services



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Heikki Linnakangas
Дата:
Сообщение: Re: Check that streaming replica received all data after master shutdown
Следующее
От: Magnus Hagander
Дата:
Сообщение: Re: EXEC_BACKEND + logging_collector=on is broken