Return-Path: postarch
Received: by postgres.Berkeley.EDU (5.61/1.29)
	id AA17027; Fri, 10 Apr 92 13:43:16 -0700
Message-Id: <9204102043.AA17027@postgres.Berkeley.EDU>
From: postarch (Postgres Mailing Archive)
Subject: Re: running the backend interactively
To: postgres@postgres.berkeley.edu
Sender: pg_adm@postgres.berkeley.edu
Reply-To: mer@postgres.berkeley.edu
In-Reply-To: Your message of "Thu, 09 Apr 92 08:44:03 +0700."
             <9204090639.AA24928@postgres.Berkeley.EDU> 
Date: Fri, 10 Apr 92 13:42:54 PDT

you write:
> Dear Postgres group,
> 
> I have some problems with running the backend interactively.
> First the postmaster is killed, then the backend is started (postgres -s geo).
> After giving the correct answer to the first query, the backend crashes.
> The reason for using the backend interactively, is that I want to do
> some performance measurements.
> 
> This used to work in earlier versions, but now (on my sparc under 
> sunos 4.0.1) Postgres V3.1 crashes. Any clues? Or alternatives for
> doing performance measurements.

This should work.  Are you saying that the same set of queries works when
you are running under the postmaster?  That would be very strange, as it
shouldn't make a difference.


Jeff Meredith
mer@postgres.berkeley.edu

p.s. For those of you who have never heard of running the backend
     interactively... This mode of operation is only used for debugging
     and measuring raw backend performance.  It is not intended for
     regular use.  Without the postmaster, concurrently backends do not
     share memory and therefore you will not have any concurrency
     control.  This could easily lead to strange and unexpected results.