pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Scott Marlowe <smarlowe@qwest.net>
To: Kris Kiger <kris@musicrebellion.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Large file support needed?  Trying to identify root of
Date: Mon, 19 Jul 2004 14:07:54 -0600
Message-ID: <1090267674.709.5.camel@localhost.localdomain> (raw)
In-Reply-To: <40FC20F0.1000402@musicrebellion.com>
References: <40F6A366.5040701@musicrebellion.com>
	<40F6B86B.3020400@spacemonkeylabs.com>
	<40F6DC6F.4000707@musicrebellion.com>
	<40FC20F0.1000402@musicrebellion.com>

On Mon, 2004-07-19 at 13:28, Kris Kiger wrote:
> I've got a database that is a single table with 5 integers, a timestamp 
> with time zone, and a boolean.  The table is 170 million rows in length. 
>  The contents of the tar'd dump file it produced using:
>     pg_dump -U postgres -Ft test > test_backup.tar
> is: 8.dat (approximately 8GB), a toc, and restore.sql.  
> 
> No errors are reported on dump, however, when a restore is attempted I get:
> 
> ERROR:  unexpected message type 0x58 during COPY from stdin
> CONTEXT:  COPY test_table, line 86077128: ""
> ERROR:  could not send data to client: Broken pipe
> CONTEXT:  COPY test_table, line 86077128: ""
> 
> I am doing the dump & restore on the same machine.
> 
> Any ideas?  If the file is too large, is there anyway postgres could 
> break it up into smaller chunks for the tar when backing up?  Thanks for 
> the help!

How, exactly, are you restoring?  Doing things like:

cat file|pg_restore ...

can cause problems because cat is often limited to 2 gigs on many OSes. 
Just use a redirect:

psql dbname <file




view thread (4+ messages)  latest in thread

Message-ID: <1090267674.709.5.camel@localhost.localdomain>
Permalink:  ../1090267674.709.5.camel@localhost.localdomain/
Also on:    postgresql.org/message-id/1090267674.709.5.camel@localhost.localdomain

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: smarlowe@qwest.net, kris@musicrebellion.com
  Subject: Re: Large file support needed?  Trying to identify root of
  In-Reply-To: <1090267674.709.5.camel@localhost.localdomain>
  References: <40F6A366.5040701@musicrebellion.com> <40F6B86B.3020400@spacemonkeylabs.com> <40F6DC6F.4000707@musicrebellion.com> <40FC20F0.1000402@musicrebellion.com> <1090267674.709.5.camel@localhost.localdomain>

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

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