Sorry Steve, I missed the "reply all" by 3 pixels :)
> > > tar -cf -
> > >
> > > the '-f -' says take input.
> >
> > That would be to write to stdout :) I can't figure out how to accept
> > from stdin :(
> >
> > -f is where the send the output, either a file, a device (such as
> > tape) or stdout (aka '-')
>
> Not quite. tar cf - will pipe to stdout, but tar xf - will pipe from
> stdin.
Yes, true; my head was in "tar c" mode :)
> For the OP's problem, I'd try piping through dd as a file buffer, and
> run sync on completion. Is there a /dev/rst0, like on some of the old
> unixes (doesn't look like it after checking my CentOS 4 server)? The
> difference was that rst0 was unbuffered, and st0 was buffered. Either
> way, the sync may help.
There's no /dev/rst0 block device, but I'm more familiar with tar than dd,
so I think I'll just rewrite the script to tar to a temp file first :)
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?
THINK BEFORE YOU PRINT - Save paper if you don't really need to print this
*******************Confidentiality and Privilege Notice*******************
The material contained in this message is privileged and confidential to
the addressee. If you are not the addressee indicated in this message or
responsible for delivery of the message to such person, you may not copy
or deliver this message to anyone, and you should destroy it and kindly
notify the sender by reply email.
Information in this message that does not relate to the official business
of Weatherbeeta must be treated as neither given nor endorsed by Weatherbeeta.
Weatherbeeta, its employees, contractors or associates shall not be liable
for direct, indirect or consequential loss arising from transmission of this
message or any attachments
e-mail.
