| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: assertion at postmaster start |
| Date: | 2019-06-17 17:38:54 |
| Message-ID: | 10852.1560793134@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andres Freund <andres(at)anarazel(dot)de> 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 process" is afaict only used for actual backends, not other
> types of processes. But we've not yet seen "database system is ready to
> accept accept connections", so IIRC it could only be a "dead_end" type
> backend? But we didn't yet see an error from that...
> Seems to indicate a logic error in postmaster's state machine. Perhaps
> something related to dead_end processes?
So if Andres is guessing right, this must be from something trying to
connect before the postmaster is ready? Seems like that could be
tested for ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2019-06-17 17:39:43 | Re: UCT (Re: pgsql: Update time zone data files to tzdata release 2019a.) |
| Previous Message | Tom Lane | 2019-06-17 17:35:46 | Re: initial random incompatibility |