Re: BUG #15804: Assertion failure when using logging_collector with EXEC_BACKEND

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Yuli Khodorkovskiy <yuli(dot)khodorkovskiy(at)crunchydata(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15804: Assertion failure when using logging_collector with EXEC_BACKEND
Date: 2019-05-23 14:17:50
Message-ID: fdd04ba4-b644-faa8-09fd-c9f6cf7b0658@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 2019-05-19 04:10, Andres Freund wrote:
>> (I'm also getting annoyed that Peter, as the original author of this
>> commit, isn't doing anything about the issue.)
>
> Yea, I'm confused / annoyed about that too.

I was traveling, and the subject line didn't yell "problem with beta1".

>> I wouldn't be totally opposed to un-reverting after beta1, if a
>> better-tested patch emerges. But we don't have such a patch today
>> and I don't see how we'll get there this weekend.
>
> Right. I think if somebody puts some elbow grease into that that'd be a
> reasonable course. But so far Peter's not showing up, so ...

After rereading the entire discussion, I don't have much enthusiasm for
trying to fix this for PG12. It's worth trying again in the future.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2019-05-23 15:27:33 Re: BUG #15804: Assertion failure when using logging_collector with EXEC_BACKEND
Previous Message PG Bug reporting form 2019-05-23 14:05:59 BUG #15817: NO access to any server after changing the pgadmin4 user password