From: Tatiana Motova <t.motova@inform-link.co.uk>
To: Robert Treat <xzilla@users.sourceforge.net>
Cc: pgsql-admin@postgresql.org
Subject: Re: pg_dump problem
Date: Fri, 28 Mar 2003 11:50:36 -0000
Message-ID: <004201c2f520$4bdd2d20$0101010a@vaio> (raw)
References: <004101c2efd5$e2131890$0101010a@vaio>
<1048533104.13853.309.camel@camel>
<01cf01c2f239$febeccd0$0101010a@vaio>
<1048796031.13799.1270.camel@camel>
Unfortunately not.
pg_dump makes it's work without reporting any errors with -Fc but pg_restore
fails:
pg_restore: [archiver (db)] error returned by PQputline
I could try upgrading to 7.3 but i need to keep the database data anyway.
Tatiana.
----- Original Message -----
From: "Robert Treat" <xzilla@users.sourceforge.net>
To: "Tatiana Motova" <t.motova@inform-link.co.uk>
Cc: <pgsql-admin@postgresql.org>
Sent: Thursday, March 27, 2003 8:13 PM
Subject: Re: [ADMIN] pg_dump problem
> Did the -Fc workaround work? I tried to do a little digging to find out
> the heart of the problem but didn't come up with much. You might want to
> post to -bugs, or better yet try upgrading to 7.3
>
> Robert Treat
>
> On Mon, 2003-03-24 at 14:17, Tatiana Motova wrote:
> > Version 7.2.2, i had same problems when using version 7.1.3 as well.
> >
> > ----- Original Message -----
> > From: "Robert Treat" <xzilla@users.sourceforge.net>
> > To: "Tatiana Motova" <t.motova@inform-link.co.uk>
> > Cc: <pgsql-admin@postgresql.org>
> > Sent: Monday, March 24, 2003 7:11 PM
> > Subject: Re: [ADMIN] pg_dump problem
> >
> >
> > > On Fri, 2003-03-21 at 13:15, Tatiana Motova wrote:
> > > > Hi all,
> > > >
> > > > i have a problem dumping the database containing blobs.
> > > >
> > > > The database has pdf files stored in one of the tables and when
there
> > > > are let say 10 files in it, pg_dump works perfectly, but when about
> > > > 400Mb of files are loaded into db, pg_dump fails with the following
> > > > message:
> > > >
> > > > pg_dump -a -b -Ft -f bdata_030321.tar -v mydb
> > > > ...
> > > > pg_dump: [tar archiver] could not write to tar member (wrote 872,
> > > > attempted 8191)
> > > >
> > > > It's not a matter of available disk space, there's plenty of it.
> > > >
> > >
> > > Haven't seen any other response on this one.... This bug used to exist
> > > in the 7.1.x versions, but I think it was fixed in one of the 7.2.x
> > > releases. Can you post your version info? In the meantime you might be
> > > able to work around it by using the -Fc instead.
> > >
> > > Robert Treat
>
>
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: t.motova@inform-link.co.uk, xzilla@users.sourceforge.net
Subject: Re: pg_dump problem
In-Reply-To: <004201c2f520$4bdd2d20$0101010a@vaio>
References: <004101c2efd5$e2131890$0101010a@vaio> <1048533104.13853.309.camel@camel> <01cf01c2f239$febeccd0$0101010a@vaio> <1048796031.13799.1270.camel@camel> <004201c2f520$4bdd2d20$0101010a@vaio>
* 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