Return-Path: owner-postman 
Delivery-Date: Tue, 10 May 94 19:25:52 -0700
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 RAA12793 for postgres-redist; Tue, 10 May 1994 17:00:13 -0700
Resent-From: POSTGRES mailing list <postman@postgres.Berkeley.EDU>
Resent-Message-Id: <199405110000.RAA12793@nobozo.CS.Berkeley.EDU>
Sender: owner-postman@postgres.Berkeley.EDU
X-Return-Path: owner-postman
Received: from faerie.CS.Berkeley.EDU (faerie.CS.Berkeley.EDU [128.32.149.14]) by nobozo.CS.Berkeley.EDU (8.6.4/8.6.3) with ESMTP id RAA12783 for <postgres@postgres.Berkeley.EDU>; Tue, 10 May 1994 17:00:12 -0700
Received: from localhost (localhost [127.0.0.1]) by faerie.CS.Berkeley.EDU (8.6.4/8.1B) with SMTP id QAA00701; Tue, 10 May 1994 16:59:47 -0700
Message-Id: <199405102359.QAA00701@faerie.CS.Berkeley.EDU>
X-Authentication-Warning: faerie.CS.Berkeley.EDU: Host localhost didn't use HELO protocol
From: aoki@postgres.Berkeley.EDU (Paul M. Aoki)
To: peter@pitre.sub.org (Peter Fuetterer)
Cc: postgres@postgres.Berkeley.EDU
Subject: Re: problems to destroy an user 
Reply-To: aoki@postgres.Berkeley.EDU (Paul M. Aoki)
In-reply-to: Your message of Tue, 10 May 1994 20:13:45 +0200 
	     <9405101813.AA00463@pluto.pitre.sub.org> 
Date: Tue, 10 May 94 16:59:47 -0700
X-Sender: aoki@postgres.Berkeley.EDU
Resent-To: postgres-redist@postgres.Berkeley.EDU
X-Mts: smtp
Resent-Date: Tue, 10 May 94 17:00:12 -0700
Resent-XMts: smtp

peter@pitre.sub.org (Peter Fuetterer) writes:
> WARN:May 10 19:51:07:pg_atoi: error in " 120         ": can't parse "        
> destroyuser: database access failed - exiting... 

kai petzke has mentioned that the pg_atoi parsing code can be modified
to be more forgiving trailing spaces.  i'm just afraid of modifying the
behavior of that code since some of the "built in" composite numeric
data types expect certain behavior from atoi and strtol (which was the 
reason for the separate atoi code -- different people's c library atoi 
code behaved in funny ways)

it's easy enough to fix by dinking the script.  this is what i did.

*** 1.8	1994/03/20 03:17:53
--- destroyuser.sh	1994/04/21 19:39:55
***************
*** 1,6 ****
  #!/bin/sh
  #
! # $Header: /usr/local/devel/postgres/src/bin/destroyuser/RCS/destroyuser.sh,v 1.8 1994/03/20 03:17:53 aoki Exp $
  #
  # Note - this should NOT be setuid.
  #
--- 1,6 ----
  #!/bin/sh
  #
! # $Header: /usr/local/devel/postgres/src/bin/destroyuser/RCS/destroyuser.sh,v 1.9 1994/04/21 19:37:34 aoki Exp $
  #
  # Note - this should NOT be setuid.
  #
***************
*** 98,104 ****
      exit 1
  fi
  
! SYSID=$RES
  
  #
  # destroy the databases owned by the deleted user.  First, use this query
--- 98,104 ----
      exit 1
  fi
  
! SYSID=`echo $RES | sed 's/ //g'`
  
  #
  # destroy the databases owned by the deleted user.  First, use this query
--
  Paul M. Aoki  |  CS Div., Dept. of EECS, UCB  |  aoki@postgres.Berkeley.EDU
                |  Berkeley, CA 94720           |  ...!uunet!ucbvax!aoki

===============================================================================
    To add/remove yourself from the POSTGRES mailing list: send mail with 
    the subject line ADD or DEL to "postgres-request@postgres.Berkeley.EDU"

    If this fails, send mail to "post_questions@postgres.Berkeley.EDU" and
    a human will deal with it.  DO NOT post to the "postgres" mailing list.
===============================================================================