Re: BUG #5622: Query failed: server closed the connection unexpectedly

From: Thue Janus Kristensen <thuejk(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5622: Query failed: server closed the connection unexpectedly
Date: 2010-08-19 22:46:52
Message-ID: AANLkTin4miDoeFRqrqOr=LO17j5MLEpLNciAQ3WSGhcB@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, Aug 19, 2010 at 5:19 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Thue Janus Kristensen <thuejk(at)gmail(dot)com> writes:
> > I finally succeeded in creating a test case, after much experimentation.
> > Running the attached sql crashes my postgresql server 100% of the time.
>
> Cute problem.

Generating the test case was very "interesting" black box debugging. Now why
does it need at least 7 (and not 1-6) updates to that unrelated row in that
unrelated table to crash...? At least it was deterministic.

> The attached fix cures it for me; would you see if it
> solves your original case too?
>

Yes, it fixes my original problem too, thanks :).

Regards, Thue

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Steven Schlansker 2010-08-19 22:54:36 Re: COPY FROM/TO losing a single byte of a multibyte UTF-8 sequence
Previous Message Tom Lane 2010-08-19 22:24:41 Re: COPY FROM/TO losing a single byte of a multibyte UTF-8 sequence