Return-Path: owner-postman Received: from localhost.Berkeley.EDU (localhost.Berkeley.EDU [127.0.0.1]) by nobozo.CS.Berkeley.EDU (8.6.10/8.6.3) with SMTP id JAA15738 for postgres-redist; Tue, 29 Aug 1995 09:20:30 -0700 Resent-From: POSTGRES mailing list Resent-Message-Id: <199508291620.JAA15738@nobozo.CS.Berkeley.EDU> X-Authentication-Warning: nobozo.CS.Berkeley.EDU: Host localhost.Berkeley.EDU didn't use HELO protocol Sender: owner-postman@postgres.Berkeley.EDU X-Return-Path: owner-postman Received: from lamont.ldgo.columbia.edu (lamont-gate.ldgo.columbia.edu [129.236.2.30]) by nobozo.CS.Berkeley.EDU (8.6.10/8.6.3) with SMTP id JAA15973 for ; Tue, 29 Aug 1995 09:20:29 -0700 Received: from stowe.ldgo.columbia.edu.LDGO by lamont.ldgo.columbia.edu (4.1/SMI-3.2) id AA02134; Tue, 29 Aug 95 12:20:23 EDT Date: Tue, 29 Aug 95 12:20:23 EDT From: sid@lamont.ldgo.columbia.edu (sidney hellman) Message-Id: <9508291620.AA02134@lamont.ldgo.columbia.edu> Received: by stowe.ldgo.columbia.edu.LDGO (4.1/SMI-4.1) id AA00620; Tue, 29 Aug 95 12:22:40 EDT To: postgres@postgres.Berkeley.EDU Cc: sid@postgres.Berkeley.EDU Subject: backend problems and "copy to" Resent-To: postgres-redist@postgres.Berkeley.EDU Resent-Date: Tue, 29 Aug 95 09:20:30 -0700 Resent-XMts: smtp Hi there, First of all, I'm not new to programming postgres, I'm just new to the nitty-gritty of administration. We area having some problems with our psotgres 4.2 database. trying to back up one of the classes with the command "copy" from within monitor results in the following message. copy trace to "/passcal/data00/field/moma/moma.95:241:10:19.trace.ascii.new" \g Query sent to backend is "copy trace to "/passcal/data00/field/moma/moma.95:241:10:19.trace.ascii.new" " Error: No response from the backend, exiting... This is after about 15 minutes, and the output file has grown to a size of about 16.5 MB (I did expect something this large, I just didn't expect an error.) The same thing happens with something along the lines of this.. monitor -c "copy trace to stdout" -NQ moma > filename.stuff I decided to try to vacuum the DB, but the vacuum is failing with backend problems also. The DB still seems to be ok, from a users point of view. I need to back up this db, and copy it to a machine at a remote sight. Does anyone have any ideas or insight? Our normal DB guy is unreachable for the next few weeks, so I've kind of been tossed into the lion cage. Thanks in advance for any help. Sid Hellman Sid Hellman at the Passcal Instrument Center | Lamont-Doherty Earth Observatory | "It was a bizarre of Columbia University | gardening accident." sid@ldeo.columbia.edu (914)365-8728 | - David St. Hubbins ============================================================================== To add/remove yourself to/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. ============================================================================== URL: http://s2k-ftp.CS.Berkeley.EDU:8000/postgres/