Return-Path: pg_adm@postgres.berkeley.edu
Received: by postgres.Berkeley.EDU (5.61/1.29)
	id AA24740; Tue, 24 Nov 92 20:40:50 -0800
Date: Tue, 24 Nov 92 20:40:50 -0800
From: Phil Shen <philshen@cs.washington.edu>
Subject: Postgres backend question...
To: postgres@postgres.berkeley.edu
Sender: pg_adm@postgres.berkeley.edu
To: postgres@postgres.berkeley.edu
Cc: Philip Shen <philshen@cs.washington.edu>
Message-Id: <Pine.3.05.9211242023.B12349-a100000@wolf.cs.washington.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII



   What would you recommend that I do when a query sent to the backend from
   monitor seems to be locked up?  (like the index creation that I tried to
   do)  How do I get out of monitor 'nicely', without leaving a process in
   the background?

   And if I DO break out of monitor, is there a command that will allow me
   to kill a process than seems to be still running in the background that 
   won't affect the Postmaster?  (the Unix 'kill' command seems to mess up
   Postmaster)

   Is there any protection against deadlocking or recursive queries which
   can overload the system?

   Thanks for your time and energy,
   Phil