pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Pieter-Jan Savat <pieterjan.savat@barclab.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Memory/Performance issue: server closed the connection unexpectedly
Date: Tue, 11 Oct 2005 09:49:11 -0400
Message-ID: <13658.1129038551@sss.pgh.pa.us> (raw)
In-Reply-To: <434B9169.6040404@barclab.com>
References: <434B9169.6040404@barclab.com>

Pieter-Jan Savat <pieterjan.savat@barclab.com> writes:
> Now here's my problem. Updating table B works fine, but updating table A 
> makes the server "close the connection unexpectedly".

That shouldn't happen.  What shows up in the postmaster log?  If the
server is dumping core, can you get a stack trace from it?

			regards, tom lane



view thread (6+ messages)  latest in thread

Message-ID: <13658.1129038551@sss.pgh.pa.us>
Permalink:  ../13658.1129038551@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/13658.1129038551@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, pieterjan.savat@barclab.com
  Subject: Re: Memory/Performance issue: server closed the connection unexpectedly
  In-Reply-To: <13658.1129038551@sss.pgh.pa.us>
  References: <434B9169.6040404@barclab.com> <13658.1129038551@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