pg.ddx.io pgsql-sql@postgresql.org mailing list archive
help / color / mirror / Atom feedpg_dump problem
6+ messages / 6 participants
[nested] [flat]
* pg_dump problem
@ 2000-06-26 17:00 Graham Vickrage <graham@digitalplanit.com>
2000-06-26 17:50 ` Re: pg_dump problem Ed Loehr <eloehr@austin.rr.com>
0 siblings, 1 reply; 6+ messages in thread
From: Graham Vickrage @ 2000-06-26 17:00 UTC (permalink / raw)
To: pgsql-sql
I am trying to backup a production database running on v6.5 and restore it
on our test machine running v6.5.
The largest table has about 750,000 rows, the other 5 tables are very small
approx 100 rows.
When I try to restore the database using "psql -e database < db.out" I get
the error message
"query buffer max length of 16384 exceeded" after each row.
Would somebody please tell me how to increse this buffer (assuming this is
whats required to solve the problem) as I have looked though the
documentation and I am still struggling :-(
Cheers
Graham
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: pg_dump problem
2000-06-26 17:00 pg_dump problem Graham Vickrage <graham@digitalplanit.com>
@ 2000-06-26 17:50 ` Ed Loehr <eloehr@austin.rr.com>
2000-06-27 08:01 ` Re: pg_dump problem drfrog@smartt.com
0 siblings, 1 reply; 6+ messages in thread
From: Ed Loehr @ 2000-06-26 17:50 UTC (permalink / raw)
To: Graham Vickrage <graham@digitalplanit.com>; +Cc: pgsql-sql
Graham Vickrage wrote:
>
> I am trying to backup a production database running on v6.5 and restore it
> on our test machine running v6.5.
>
> The largest table has about 750,000 rows, the other 5 tables are very small
> approx 100 rows.
>
> When I try to restore the database using "psql -e database < db.out" I get
> the error message
> "query buffer max length of 16384 exceeded" after each row.
>
> Would somebody please tell me how to increse this buffer (assuming this is
> whats required to solve the problem) as I have looked though the
> documentation and I am still struggling :-(
You probably don't need to increase the buffer. More likely, there is an
unterminated string constant somewhere in db.out. Yes, that would
probably be a bug in pg_dump, but I do vaguely recall problems in 6.5*
with pg_dump. You might search deja for your error message.
Regards,
Ed Loehr
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: pg_dump problem
2000-06-26 17:00 pg_dump problem Graham Vickrage <graham@digitalplanit.com>
2000-06-26 17:50 ` Re: pg_dump problem Ed Loehr <eloehr@austin.rr.com>
@ 2000-06-27 08:01 ` drfrog@smartt.com
0 siblings, 0 replies; 6+ messages in thread
From: drfrog@smartt.com @ 2000-06-27 08:01 UTC (permalink / raw)
To: Ed Loehr <eloehr@austin.rr.com>; +Cc: Graham Vickrage <graham@digitalplanit.com>; pgsql-sql
Ed Loehr wrote:
>
> Graham Vickrage wrote:
> >
> > I am trying to backup a production database running on v6.5 and restore it
> > on our test machine running v6.5.
> >
> > The largest table has about 750,000 rows, the other 5 tables are very small
> > approx 100 rows.
> >
> > When I try to restore the database using "psql -e database < db.out" I get
> > the error message
> > "query buffer max length of 16384 exceeded" after each row.
> >
> > Would somebody please tell me how to increse this buffer (assuming this is
> > whats required to solve the problem) as I have looked though the
> > documentation and I am still struggling :-(
>
> You probably don't need to increase the buffer. More likely, there is an
> unterminated string constant somewhere in db.out. Yes, that would
> probably be a bug in pg_dump, but I do vaguely recall problems in 6.5*
> with pg_dump. You might search deja for your error message.
>
> Regards,
> Ed Loehr
i seem to remember something about this,
if i remeber right i broke out the data and inserted it back in using a
perl script
using a count loop
^ permalink raw reply [nested|flat] 6+ messages in thread
* pg_dump problem
@ 2003-01-16 06:10 Rudi Starcevic <rudi@oasis.net.au>
2003-01-01 11:34 ` Re: pg_dump problem Tomasz Myrta <jasiek@klaster.net>
2003-01-20 09:37 ` Re: pg_dump problem Bhuvan A <bhuvansql@myrealbox.com>
0 siblings, 2 replies; 6+ messages in thread
From: Rudi Starcevic @ 2003-01-16 06:10 UTC (permalink / raw)
To: pgsql-sql
Hi,
After doing a pg_dump on a database I'm unable to access the file.
My command is simply 'mv' ::
mv camper.dump20020116 camper_bak/
The error I get is ::
mv: camper.dump20020116: Value too large for defined data type
Strange. It seems to be saying the file I created is too large to handle.
Do you know where I've gone wrong ?
I just want to dump one of my databases, move it to a back up dir. then
make changes to the running database.
Thank you kindly
Regards
Rudi Starcevic
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: pg_dump problem
2003-01-16 06:10 pg_dump problem Rudi Starcevic <rudi@oasis.net.au>
@ 2003-01-01 11:34 ` Tomasz Myrta <jasiek@klaster.net>
1 sibling, 0 replies; 6+ messages in thread
From: Tomasz Myrta @ 2003-01-01 11:34 UTC (permalink / raw)
To: Rudi Starcevic <rudi@oasis.net.au>; +Cc: pgsql-sql
Rudi Starcevic wrote:
>Hi,
>
>After doing a pg_dump on a database I'm unable to access the file.
>
>My command is simply 'mv' ::
>
>mv camper.dump20020116 camper_bak/
>
>The error I get is ::
>
>mv: camper.dump20020116: Value too large for defined data type
>
>Strange. It seems to be saying the file I created is too large to handle.
>Do you know where I've gone wrong ?
>I just want to dump one of my databases, move it to a back up dir. then
>make changes to the running database.
It looks like you have not a postgres, but filesystem problem. How big is this file?
Anyway pg_dump can save filedump in gzip format, which is better for further backuping.
Regards,
Tomasz Myrta
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: pg_dump problem
2003-01-16 06:10 pg_dump problem Rudi Starcevic <rudi@oasis.net.au>
@ 2003-01-20 09:37 ` Bhuvan A <bhuvansql@myrealbox.com>
1 sibling, 0 replies; 6+ messages in thread
From: Bhuvan A @ 2003-01-20 09:37 UTC (permalink / raw)
To: pgsql-sql
> mv camper.dump20020116 camper_bak/
>
> The error I get is ::
>
> mv: camper.dump20020116: Value too large for defined data type
>
It may not be a postgresql problem. It may be due to your filesystem. Try
the documentation or mailing list of your filesystem.
regards,
bhuvaneswaran
^ permalink raw reply [nested|flat] 6+ messages in thread
end of thread, other threads:[~2003-01-20 09:37 UTC | newest]
Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2000-06-26 17:00 pg_dump problem Graham Vickrage <graham@digitalplanit.com>
2000-06-26 17:50 ` Ed Loehr <eloehr@austin.rr.com>
2000-06-27 08:01 ` drfrog@smartt.com
2003-01-16 06:10 pg_dump problem Rudi Starcevic <rudi@oasis.net.au>
2003-01-01 11:34 ` Tomasz Myrta <jasiek@klaster.net>
2003-01-20 09:37 ` Bhuvan A <bhuvansql@myrealbox.com>
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