agora inbox for postgres@postgres.berkeley.edu  

help / color / mirror / Atom feed

From: sidney hellman <sid@lamont.ldgo.columbia.edu>
To: postgres@postgres.Berkeley.EDU
Cc: sid@postgres.Berkeley.EDU
Subject: backend problems and "copy to"
Date: Tue, 29 Aug 95 12:20:23 EDT
Message-ID: <9508291620.AA02134@lamont.ldgo.columbia.edu> (raw)

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/

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: postgres@postgres.berkeley.edu
  Cc: sid@lamont.ldgo.columbia.edu, sid@postgres.Berkeley.EDU
  Subject: Re: backend problems and "copy to"
  In-Reply-To: <9508291620.AA02134@lamont.ldgo.columbia.edu>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox