Re: EXEC_BACKEND + logging_collector=on is broken

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: EXEC_BACKEND + logging_collector=on is broken
Date: 2015-01-13 19:24:31
Message-ID: 25087.1421177071@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andres Freund <andres(at)2ndquadrant(dot)com> 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 pretty much zero.

Agreed. We want this case to work for our own testing purposes, but
it's unlikely to be hurting anybody in the field.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Oskari Saarenmaa 2015-01-13 21:18:27 __attribute__ for non-gcc compilers
Previous Message Andres Freund 2015-01-13 19:21:55 Re: EXEC_BACKEND + logging_collector=on is broken