pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Scott Marlowe <scott.marlowe@gmail.com>
To: Phillip Smith <phillip.smith@weatherbeeta.com.au>
Cc: pgsql-admin@postgresql.org
Subject: Re: Backup to Tape Incomplete
Date: Tue, 26 Feb 2008 21:46:46 -0600
Message-ID: <dcc563d10802261946w5c064c66g689be5ad0563476f@mail.gmail.com> (raw)
In-Reply-To: <01fb01c878f2$44149f00$9b0014ac@wbaus090>
References: <20080227162750.5638b0e8.steve.holdoway@firetrust.com>
	<01fb01c878f2$44149f00$9b0014ac@wbaus090>

On Tue, Feb 26, 2008 at 9:38 PM, Phillip Smith
<phillip.smith@weatherbeeta.com.au> wrote:
>
>  Do we think this is a Postgres problem, a Linux problem or a problem
>  specific to my hardware setup? Was I wrong to think that I should be able to
>  stream directly from pg_dump to /dev/st0? I would have thought it *should*
>  work, but maybe I was wrong in the first place with that?

If you can dd the file onto your tape drive, then it's some weird
interaction between pg_dump and your system I'd think.  Could the be
some maximum size that you can buffer through pipes / redirects on
your machine?

I'd test to see if cat pgdumpfile.sql > /dev/st0 works or not.  If it
fails at the same approximate size, then it's something to do with
redirection.  If tar works but redirects fail, then the problem isn't
with postgresql.  i.e. do something similar to what you're doing with
pgsql and see which things fail and which ones don't.



view thread (15+ messages)  latest in thread

Message-ID: <dcc563d10802261946w5c064c66g689be5ad0563476f@mail.gmail.com>
Permalink:  ../dcc563d10802261946w5c064c66g689be5ad0563476f@mail.gmail.com/
Also on:    postgresql.org/message-id/dcc563d10802261946w5c064c66g689be5ad0563476f@mail.gmail.com

 · 

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: scott.marlowe@gmail.com, phillip.smith@weatherbeeta.com.au
  Subject: Re: Backup to Tape Incomplete
  In-Reply-To: <dcc563d10802261946w5c064c66g689be5ad0563476f@mail.gmail.com>
  References: <20080227162750.5638b0e8.steve.holdoway@firetrust.com> <01fb01c878f2$44149f00$9b0014ac@wbaus090> <dcc563d10802261946w5c064c66g689be5ad0563476f@mail.gmail.com>

* 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