"Henry" <henka(at)cityweb(dot)co(dot)za> writes:
> Before I run this again, what's the best way to proceed to get a core dump
> so I can run a gdb backtrace to provide more info? Simply 'ulimit -c
> 5242880' as user postgres and restart PG?
I'd use "ulimit -c unlimited", myself, rather than making arbitrary
assumptions about how big the corefile might be.
Also, make sure the ulimit command is effective in the shell that will
actually launch the postmaster. This can be tricky if your PG launch
script uses "su". If you're using the RH or PGDG RPMs' initscript,
I'd suggest putting the ulimit command in ~postgres/.bash_profile.
regards, tom lane
In response to
pgsql-bugs by date
|Next:||From: Arturas Mazeika||Date: 2010-10-31 01:30:13|
|Subject: Re: BUG #5735: pg_upgrade thinks that it did not start the
|Previous:||From: Greg Stark||Date: 2010-10-30 19:19:31|
|Subject: Re: BUG #5732: parsing of: "WHERE mycol=123AND ..."|