Postgres Pro
Downloads
Home   >   mailing lists

EXEC_BACKEND + logging_collector=on is broken - Mailing list pgsql-hackers

From Andres Freund
Subject EXEC_BACKEND + logging_collector=on is broken
Date
Msg-id 20150113182344.GF12272@alap3.anarazel.de
Whole thread Raw
Responses Re: EXEC_BACKEND + logging_collector=on is broken
List pgsql-hackers
Tree view 
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 by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Check that streaming replica received all data after master shutdown
Next
From: Magnus Hagander
Date:
Subject: Re: EXEC_BACKEND + logging_collector=on is broken