pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: JT Kirkpatrick <jt-kirkpatrick@mpsllc.com>
To: 'pgsql-admin@hub.org' <pgsql-admin@hub.org>
To: 'pgsql-sql@hub.org' <pgsql-sql@hub.org>
Subject: backend closing channel unexpectedly
Date: Thu, 22 Apr 1999 16:32:23 -0400
Message-ID: <01BE8CDD.B416B280.jt-kirkpatrick@mpsllc.com> (raw)

--BTW, the update below, when done in psql and with [. . .and ssms.autoinv 
= 101999;] added (in other words, do it for just one record), it works 
fine.  When I try to do it for multiple records, bombola!  Maybe this is 
for the sql group. . .


You know, I have asked this week how to correct some error messages I get 
when I vacuum related to TUPLE<>HEAP sizes - I thought I caused the problem 
by setting all relname to lower(relname) in pg_class and attname to 
lower(attname) in pg_attribute.  But I don't think that caused the problem. 
 I was executing an update query today, and got the message "backend 
closing channel unexpectedly".  It bombs no matter how I try to run the 
query (either from psql [update ssms set technotes = ssmsnotes.technotes 
from ssmsnotes where ssms.autoinv = ssmsnotes.autoinv;] or from within 
access97 [UPDATE ssms INNER JOIN ssmsnotes ON ssms.autoinv = 
ssmsnotes.autoinv SET ssms.technotes = ssmsnotes.technotes;].  I have tried 
several ways to run the query, but I'm pretty confident in the access97 
version - I have used it many times before on this same database (and even 
the same table) to pull over other fields.  Any idea why the old bomb 
happens?  Anywhere for me to check?  Do we just attribute it to the overall 
decline of morals in our (usa) society??

Thanks for help in advance!  jt


Message-ID: <01BE8CDD.B416B280.jt-kirkpatrick@mpsllc.com>
Permalink:  ../01BE8CDD.B416B280.jt-kirkpatrick@mpsllc.com/
Also on:    postgresql.org/message-id/01BE8CDD.B416B280.jt-kirkpatrick@mpsllc.com

 · 

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-sql@postgresql.org
  Cc: jt-kirkpatrick@mpsllc.com, pgsql-admin@hub.org, pgsql-sql@hub.org
  Subject: Re: backend closing channel unexpectedly
  In-Reply-To: <01BE8CDD.B416B280.jt-kirkpatrick@mpsllc.com>
  References: <01BE8CDD.B416B280.jt-kirkpatrick@mpsllc.com>

* 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