pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ryan Bradetich <ryan_bradetich@hp.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-sql@postgresql.org
Subject: Re: Problem with pg_dumpall
Date: Tue, 27 Jun 2000 17:14:35 -0600
Message-ID: <3959355B.762D586C@hp.com> (raw)
References: <3958D5EA.82E74C68@hp.com>
	<14979.962142613@sss.pgh.pa.us>
	<395922BA.2F477593@hp.com>
	<16833.962143321@sss.pgh.pa.us>

Tom Lane wrote:

> Ryan Bradetich <ryan_bradetich@hp.com> writes:
> > Tom Lane wrote:
> >> Ryan Bradetich <ryan_bradetich@hp.com> writes:
> >>>> --  dumping out the contents of Table 'medusa'
> >>>> FATAL 1:  Memory exhausted in AllocSetAlloc()
> >>>> PQendcopy: resetting connection
> >>>> SQL query to dump the contents of Table 'medusa' did not execute
> >>>> correctly.  After we read all the table contents from the backend,
> >>>> PQendcopy() failed.  Explanation from backend: 'FATAL 1:  Memory
> >>>> exhausted in AllocSetAlloc()
> >>>> '.
> >>>> The query was: 'COPY "medusa" WITH OIDS TO stdout;
>
> Now that I look at it, it appears that COPY WITH OIDS leaks the memory
> used for the string representation of the OIDs.  That'd probably cost
> you 32 bytes or so of backend memory per row --- which you'd get back
> at the end of the COPY, but small comfort if you ran out before that.
>
> Is the table large enough to make that a plausible explanation?
>
>                         regards, tom lane

Tom,

This table is very large so that could be the problem.

Here are the startup parameters I am using (in case it matters):
    -B 1024
    -S
    -o -F
    -o -o /home/postgres/nohup.out
    -i
    -p 5432
    -D/data08


nohup su - postgres -c "/opt/pgsql/bin/postmaster -B 1024 -S -o \"-F\" -o
\"-o /home/postgres/nohup.out\" -i -p 5432 -D/data08"
procman=# select count(*) from medusa;
  count
---------
 6986499
(1 row)



FYI:

That was the problem.  Good job at spotting that Tom.  I just successfully
completed a backup without using the -o
option to pg_dumpall.

Thanks again for the help!

- Ryan


--
Ryan Bradetich
AIT Operations
Unix Platform Team






view thread (6+ messages)  latest in thread

Message-ID: <3959355B.762D586C@hp.com>
Permalink:  ../3959355B.762D586C@hp.com/
Also on:    postgresql.org/message-id/3959355B.762D586C@hp.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-sql@postgresql.org
  Cc: ryan_bradetich@hp.com, tgl@sss.pgh.pa.us
  Subject: Re: Problem with pg_dumpall
  In-Reply-To: <3959355B.762D586C@hp.com>
  References: <3958D5EA.82E74C68@hp.com> <14979.962142613@sss.pgh.pa.us> <395922BA.2F477593@hp.com> <16833.962143321@sss.pgh.pa.us> <3959355B.762D586C@hp.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