Resent-From: POSTGRES mailing list <postman@postgres.Berkeley.EDU>
Resent-Message-Id: <199311232016.MAA00252@nobozo.CS.Berkeley.EDU>
Sender: owner-postman@postgres.Berkeley.EDU
From: John Peter Lee <jlee@cs.uml.edu>
Message-Id: <199311232016.AA20071@cs.uml.edu>
Subject: killing process while creating index, and more...
To: postgres@postgres.Berkeley.EDU
Date: Tue, 23 Nov 1993 15:16:14 -0500 (EST)
Content-Type: text
Content-Length: 1163      
Resent-To: postgres-dist@postgres.Berkeley.EDU
Resent-Date: Tue, 23 Nov 93 12:16:52 -0800
Resent-XMts: smtp

Hi:

  I would like to know what the effect would be if I had killed my process
  that was building indexes on a newly created database. It seems that the
  b-tree building is taking an extremely long time, and I'd like to stop
  for now and do some other work with the database. If I killed the 
  process and deleted the index (can I do that, or only delete classes ?),
  would all be well ??? Would anything become corrupted such that the 
  database is unreadable ??? It took over 25 hours to construct the data-
  base, and I don't want to make it unusable.

  Also, I never heard back from yesterday's question concerning the 
  potential memory leak in Postgres. I had to use PQreset every 9000
  appends to clear out the resident set of the postgres process. Any
  news on this ?

  thanks,

  jp

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
JP Lee               Institute for Visualization and Perception Research	
jlee@cs.uml.edu                    University of Massachusetts at Lowell 
(508) 934-3384			      1 University Ave. Lowell, MA 01854

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~