Return-Path: postarch
Received: by postgres.Berkeley.EDU (5.61/1.29)
	id AA15490; Thu, 28 May 92 09:25:07 -0700
Message-Id: <9205281625.AA15490@postgres.Berkeley.EDU>
From: postarch (Postgres Mailing Archive)
Subject: Re: queries per transaction
To: postgres@postgres.berkeley.edu
Sender: pg_adm@postgres.berkeley.edu
Reply-To: mer@postgres.berkeley.edu
In-Reply-To: Your message of "Tue, 26 May 92 17:40:12 PDT."
             <9205262129.AA02190@vanguard.inpe.br> 
Date: Thu, 28 May 92 09:20:32 PDT

you write:

> But sometimes I get messages like that:
> 
> ...
> replace GeoClass (label = "0-2%", model = 3)where GeoClass.catid = 5 and GeoC
 +las
>    s.classid = 1Error: No response from the backend, exiting...
> ...
> 
> Is there any limitation to the number of queries or tables per transaction ?
> Is there something I could do related to postgres to gain more stability ?
> I am not a unix expert and sometimes is difficult to decide if the error come
 +s f
>    rom SUNOS or POSTGRES...

>Error: No response from the backend, exiting...

This usually indicates a backend crash.  Check for a core dump in
$POSTGRESHOME/data/base/<dbname> and send us a bug report with a stack trace
(using your favorite debugger as described in the documentation).

The hard wired limit in v3.1 for the number of commands per transaction is
256.  Version 4 will extend this limit to 65535, and it will be more vocal
when you overstep the bounds.

If you are ever in doubt as to whether a problem arises from postgres or
from the underlying os, it is probably a safe bet to assume that postgres is
the culprit.


Jeff Meredith
mer@postgres.berkeley.edu