| From: | Francisco Reyes <lists(at)stringsutils(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(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 15:25:50 |
| Message-ID: | cone.1181921150.10404.53974.5001@35st.simplicato.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Alvaro Herrera writes:
> 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
pg_ctl -l <file> didn't work.
Trying now with changes to postgreql.conf:
redirect_stderr = on
log_directory = '/data/logs'
log_filename = 'postgresql-%Y-%m-%d.log
log_error_verbosity = verbose
And increased all error levels to debug1
That looks promissing already.. see errors going to the file.
Trying again. will be a few hours before it gets to the line where it runs
out of memory.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | MC Moisei | 2007-06-15 16:09:49 | Re: Postmaster processes taking all the CPU |
| Previous Message | Alvaro Herrera | 2007-06-15 15:18:44 | Re: DeadLocks..., DeadLocks... |