Re: pgsql: Make new crash restart test a bit more robust.

From: Andres Freund <andres(at)anarazel(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Make new crash restart test a bit more robust.
Date: 2017-09-19 20:25:18
Message-ID: 20170919202518.au4ngniiwdsyewbp@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On 2017-09-19 15:24:49 -0400, Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
> > Checkining on calliphoridae why that's not sufficient - the machine's
> > busy, so the build & test will take a bit.
>
> FWIW, prairiedog got through the recovery tests this time --- run's
> still going though.

So this is geniuinely interesting. When the machine is really loaded (as
in 6 animals running on a vm at the same time, incuding valgrind), psql
sometimes doesn't get the WARNING message from a shutdown. Instead it
gets
# psql:<stdin>:3: server closed the connection unexpectedly
# This probably means the server terminated abnormally
# before or while processing the request.
# psql:<stdin>:3: connection to server was lost

We can obviously easily make the test accept both - but are we ok with
the client sometimes not getting the message?

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2017-09-19 20:25:31 Re: pgsql: Speedup pgstat_report_activity by moving mb-aware truncation to
Previous Message Andres Freund 2017-09-19 20:03:51 pgsql: Speedup pgstat_report_activity by moving mb-aware truncation to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2017-09-19 20:25:52 Re: Boom filters for hash joins (was: A design for amcheck heapam verification)
Previous Message Ashwin Agrawal 2017-09-19 20:23:58 "inconsistent page found" with checksum and wal_consistency_checking enabled