| From: | Janning Vygen <vygen(at)kicktipp(dot)de> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: PANIC: corrupted item pointer |
| Date: | 2012-04-11 14:16:35 |
| Message-ID: | 4F859243.4090505@kicktipp.de |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Am 06.04.2012 23:49, schrieb Jeff Davis:
>> No, i didn't found any in my postgresql dirs. Should i have a core file
>> around when i see a segmentation fault? What should i look for?
>
> It's an OS setup thing, but generally a crash will generate a core file
> if it is allowed to. Use "ulimit -c unlimited" on linux in the shell
> that starts postgresql and I think that will work. You can test it by
> manually doing a "kill -11" on the pid of a backend process.
My system was setup with
$ cat /proc/32741/limits
Limit Soft Limit Hard Limit
Units
...
Max core file size 0 unlimited
bytes
...
to bad, no core dump.
I will follow instructions on peters blog here
<http://petereisentraut.blogspot.de/2011/06/enabling-core-files-for-postgresql-on.html>
So next time i'll be ready to handle this issue.
Thanks a lot for your help, jeff.
regards
Janning
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Nolan | 2012-04-11 14:38:05 | Re: [streaming replication] 9.1.3 streaming replication bug ? |
| Previous Message | Cédric Villemain | 2012-04-11 14:08:59 | Re: Searchable chess positions in a Postgress DB |