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 15:55:06 -0600
Message-ID: <395922BA.2F477593@hp.com> (raw)
References: <3958D5EA.82E74C68@hp.com>
	<14979.962142613@sss.pgh.pa.us>

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;
>
> Hmm.  What is the full definition of that table?  (pg_dump -s -t medusa
> would do.)
>
>                         regards, tom lane

Tom,


boi260 /data08 $ pg_dump -s -t medusa procman
\connect - postgres
CREATE TABLE "medusa" (
        "host_id" int4,
        "timestamp" timestamp,
        "current" int4,
        "catagory" text,
        "cat_desc" text,
        "anomaly" text
);
CREATE  INDEX "medusa_catagory_key" on "medusa" using btree ( "catagory"
"text_ops" );
CREATE  INDEX "medusa_host_id_key" on "medusa" using btree ( "host_id"
"int4_ops" );
CREATE  INDEX "medusa_current_key" on "medusa" using btree ( "current"
"int4_ops" );

Ryan





view thread (6+ messages)  latest in thread

Message-ID: <395922BA.2F477593@hp.com>
Permalink:  ../395922BA.2F477593@hp.com/
Also on:    postgresql.org/message-id/395922BA.2F477593@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: <395922BA.2F477593@hp.com>
  References: <3958D5EA.82E74C68@hp.com> <14979.962142613@sss.pgh.pa.us> <395922BA.2F477593@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