Skip site navigation (1) Skip section navigation (2)

Re: Problem with pg_dumpall

From: Ryan Bradetich <ryan_bradetich(at)hp(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: Problem with pg_dumpall
Date: 2000-06-27 21:55:06
Message-ID: 395922BA.2F477593@hp.com (view raw or flat)
Thread:
Lists: pgsql-sql
Tom Lane wrote:

> Ryan Bradetich <ryan_bradetich(at)hp(dot)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



In response to

Responses

pgsql-sql by date

Next:From: Tom LaneDate: 2000-06-27 22:02:01
Subject: Re: Problem with pg_dumpall
Previous:From: Tom LaneDate: 2000-06-27 21:50:13
Subject: Re: Problem with pg_dumpall

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group