pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Donald Fraser <postgres@kiwi-fraser.net>
Cc: [ADMIN] <pgsql-admin@postgresql.org>
Subject: Re: Strange message followed by server crash
Date: Thu, 31 Aug 2006 22:01:36 -0400
Message-ID: <27236.1157076096@sss.pgh.pa.us> (raw)
In-Reply-To: <008c01c6c855$35f6cd20$7d64a8c0@demolish1>
References: <003401c6c837$8dc6cb90$7d64a8c0@demolish1>
	<23160.1156513462@sss.pgh.pa.us>
	<008c01c6c855$35f6cd20$7d64a8c0@demolish1>

"Donald Fraser" <postgres@kiwi-fraser.net> writes:
> Log messages:
> <1Tmenteshvili 10709 2006-08-24 17:48:19 BST 0> ERROR:  invalid =
> message format
> < 3670 2006-08-24 17:48:19 BST > LOG:  server process (PID 10709) was =
> terminated by signal 11

> At the same time, an engineer, who thought nobody was in the =
> building, was working on the network and changing a network switch.

I tried to reproduce this by using gdb to force the "invalid message
format" failure --- that is, deliberately changing one of the values 
pq_getmsgend compares.  No luck, the backend issued the error and
continued just as it should.  My best guess now that the crash was not
directly related to that error, but was caused by insufficiently robust
processing of whatever garbage was received following that.  However,
with no clue what that garbage might have looked like, there's too many
possible code paths to try to chase through with no leads.

Anyone care to do some random-data stress testing, ie, connect to a
backend and squirt random data at it to see if you can make it crash
rather than just complain and disconnect?  Be prepared to show a backend
stack trace and the exact data sent if you succeed.

			regards, tom lane



view thread (6+ messages)

Message-ID: <27236.1157076096@sss.pgh.pa.us>
Permalink:  ../27236.1157076096@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/27236.1157076096@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, postgres@kiwi-fraser.net
  Subject: Re: Strange message followed by server crash
  In-Reply-To: <27236.1157076096@sss.pgh.pa.us>
  References: <003401c6c837$8dc6cb90$7d64a8c0@demolish1> <23160.1156513462@sss.pgh.pa.us> <008c01c6c855$35f6cd20$7d64a8c0@demolish1> <27236.1157076096@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox