On 2019-Aug-26, Tom Lane wrote:
> I wrote:
> > I propose the attached. I'm inclined to think that the risk/benefit
> > of back-patching this is not very good, so I just want to stick it in
> > HEAD, unless somebody can explain why dead_end children are likely to
> > crash in the field.
>
> Pushe
I wrote:
> I propose the attached. I'm inclined to think that the risk/benefit
> of back-patching this is not very good, so I just want to stick it in
> HEAD, unless somebody can explain why dead_end children are likely to
> crash in the field.
Pushed at ee3278239.
I'm still curious as to the ex
I wrote:
> I think what this demonstrates is that that Assert is just wrong:
> we *can* reach PM_RUN with the flag still set, so we should do
> StartupStatus = STARTUP_NOT_RUNNING;
> FatalError = false;
> - Assert(AbortStartTime == 0);
I wrote:
> Andres Freund writes:
>> On 2019-06-15 12:09:50 -0400, Alvaro Herrera wrote:
>>> Once in a blue moon I get this assertion failure on server start:
>>> TRAP: FailedAssertion("!(AbortStartTime == 0)", Archivo:
>>> "/pgsql/source/master/src/backend/postmaster/postmaster.c", Linea: 2957)
Andres Freund writes:
> On 2019-06-15 12:09:50 -0400, Alvaro Herrera wrote:
>> Once in a blue moon I get this assertion failure on server start:
>> TRAP: FailedAssertion(«!(AbortStartTime == 0)», Archivo:
>> «/pgsql/source/master/src/backend/postmaster/postmaster.c», Línea: 2957)
> And "server p
Hi,
On 2019-06-15 12:09:50 -0400, Alvaro Herrera wrote:
> Once in a blue moon I get this assertion failure on server start:
>
> 2019-06-15 12:00:29.650 -04 [30080] LOG: iniciando PostgreSQL 12beta1 on
> x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 7.4.0-1ubuntu1~18.04) 7.4.0,
> 64-bit
> 2019-0
Once in a blue moon I get this assertion failure on server start:
2019-06-15 12:00:29.650 -04 [30080] LOG: iniciando PostgreSQL 12beta1 on
x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 7.4.0-1ubuntu1~18.04) 7.4.0, 64-bit
2019-06-15 12:00:29.650 -04 [30080] LOG: escuchando en la dirección IPv4
«
