| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Francisco Reyes <lists(at)stringsutils(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: pg_restore out of memory |
| Date: | 2007-06-15 13:19:37 |
| Message-ID: | 20070615131937.GC4717@alvh.no-ip.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Francisco Reyes wrote:
> Tom Lane writes:
>
> >The memory dump only comes out on stderr (I think because of paranoia
> >about running out of memory while trying to report we're out of memory).
> >Can you get the postmaster's stderr output?
>
> >From stderr
>
> pg_restore: restoring data for table "message_attachments"
> pg_restore: [archiver (db)] Error from TOC entry 2146; 0 988154 TABLE DATA
> message_attachments pgsql
This is pg_restore's stderr. What Tom wants to see is postmaster's. It
is probably redirected (hopefully to a file, but regretfully it is
common to see it go to /dev/null) on the init script that starts the
service.
If it's going to /dev/null, change it to somewhere more reasonable and
try again. Or you could start the postmaster by hand on a terminal
under your control.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-06-15 13:32:35 | Re: pg_restore out of memory |
| Previous Message | Gregory Stark | 2007-06-15 13:17:46 | Re: pg_restore out of memory |