Return-Path: owner-postman Received: from localhost (localhost [127.0.0.1]) by nobozo.CS.Berkeley.EDU (8.6.4/8.6.3) with SMTP id RAA16673 for postgres-dist; Sun, 27 Mar 1994 17:41:35 -0800 Resent-From: POSTGRES mailing list Resent-Message-Id: <199403280141.RAA16673@nobozo.CS.Berkeley.EDU> X-Authentication-Warning: nobozo.CS.Berkeley.EDU: Host localhost didn't use HELO protocol Sender: owner-postman@postgres.Berkeley.EDU X-Return-Path: owner-postman Received: from newberry.uoregon.edu (newberry.uoregon.edu [128.223.95.232]) by nobozo.CS.Berkeley.EDU (8.6.4/8.6.3) with ESMTP id RAA16664 for ; Sun, 27 Mar 1994 17:41:34 -0800 Received: from localhost (ken@localhost) by newberry.uoregon.edu (8.6.4/8.6.4) id RAA20152 for postgres@postgres.Berkeley.EDU; Sun, 27 Mar 1994 17:41:32 -0800 Date: Sun, 27 Mar 1994 17:41:32 -0800 From: Ken Dueker Message-Id: <199403280141.RAA20152@newberry.uoregon.edu> To: postgres@postgres.Berkeley.EDU Subject: how to kill locked jobs ? Resent-To: postgres-dist@postgres.Berkeley.EDU Resent-Date: Sun, 27 Mar 94 17:41:35 -0800 Resent-XMts: smtp i have gotten into situations were the back-end has locked up when i accidentally re-define index's. Unfortunately, these jobs are owned by root - and without su password i cannot kill these hung jobs. I have combed the doc for clues as to how to change the ownership of the back-end job to little avail ... any suggestions ? ken