| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Carrington, Matthew (Produban)" <Matthew(dot)Carrington(at)Produban(dot)co(dot)uk> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: pg_upgrade: out of memory |
| Date: | 2012-09-28 14:15:33 |
| Message-ID: | 22246.1348841733@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Carrington, Matthew (Produban)" <Matthew(dot)Carrington(at)Produban(dot)co(dot)uk> writes:
> I've tried to explore the issue a bit more using 9.2.1. Here's a trace of the build and dump tests ...
As long as you're building your own copy, how about building with
--enable-debug and getting a stack trace showing where the error is
being thrown? Setting a breakpoint at exit_horribly() ought to do
the trick. To be concrete:
gdb pg_dump
gdb> b exit_horribly
gdb> run --port 65432 ... rest of command line for pg_dump ...
... wait for breakpoint to be hit, then ...
gdb> bt
... copy and paste the printout here ...
gdb> quit
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Carrington, Matthew (Produban) | 2012-09-28 14:58:09 | Re: pg_upgrade: out of memory |
| Previous Message | Yelai, Ramkumar IN BLR STS | 2012-09-28 13:01:46 | Re: Re: Need help in reclaiming disk space by deleting the selected records |