Re: [HACKERS] EXEC_BACKEND + logging_collector=on is broken

2015-01-13 Thread Andres Freund
On 2015-01-13 20:21:55 +0100, Andres Freund wrote: > On 2015-01-13 11:10:06 -0800, Magnus Hagander wrote: > > EXEC_BACKEND on Windows doesn't actually use a tempfile though, so I'm > > guessing that's it. > > Ah! Then this really is fairly harmless. Will fix and backpatch anyway, > but the number

Re: [HACKERS] EXEC_BACKEND + logging_collector=on is broken

2015-01-13 Thread Tom Lane
Andres Freund writes: > On 2015-01-13 11:10:06 -0800, Magnus Hagander wrote: >> EXEC_BACKEND on Windows doesn't actually use a tempfile though, so I'm >> guessing that's it. > Ah! Then this really is fairly harmless. Will fix and backpatch anyway, > but the number of affected people should be pre

Re: [HACKERS] EXEC_BACKEND + logging_collector=on is broken

2015-01-13 Thread Andres Freund
On 2015-01-13 11:10:06 -0800, Magnus Hagander wrote: > EXEC_BACKEND on Windows doesn't actually use a tempfile though, so I'm > guessing that's it. Ah! Then this really is fairly harmless. Will fix and backpatch anyway, but the number of affected people should be pretty much zero. Greetings, And

Re: [HACKERS] EXEC_BACKEND + logging_collector=on is broken

2015-01-13 Thread Magnus Hagander
On Tue, Jan 13, 2015 at 10:23 AM, Andres Freund wrote: > 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

[HACKERS] EXEC_BACKEND + logging_collector=on is broken

2015-01-13 Thread Andres Freund
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 d