I have downloaded the following RPMs from http://yum.postgresql.org/9.2/redhat/rhel-5.6-x86_64/
postgresql92-9.2.4-1PGDG.rhel5.x86_64.rpm
postgresql92-libs-9.2.4-1PGDG.rhel5.x86_64.rpm
postgresql92-contrib-9.2.4-1PGDG.rhel5.x86_64.rpm
postgresql92-server-9.2.4-1PGDG.rhel5.x86_64.rpm
A core file was not generated. I will try with adding the ulimit command to the service script. Attached is the service script.
Thanks
Bhushan Pathak
On Fri, Jun 6, 2014 at 8:09 PM, Tom Lane <tgl@xxxxxxxxxxxxx> wrote:
Bhushan Pathak <bhushan.pathak02@xxxxxxxxx> writes:FWIW, I'd expect any such core to be generated either in postgres'
>>> Stopping postgresql service: [ OK ]
>>> Starting postgresql service: [FAILED]
>>>
>>> pgstartup log has the same line -
>>> Segmentation fault (core dumped)
>>>
>>> Where is this core dump file generated? How do we proceed further from
>>> here?
home directory or the $PGDATA directory, depending on what is
failing when. If you don't see a core, it's likely because the failing
program is running under "ulimit -c 0", which is the default environment
for daemons (for security reasons). Try adding "ulimit -c unlimited"
to the start script and/or the postgres user's ~/.bash_profile to see
if you can get a core file for debugging.
The issue seems like it must trace back to some difference in the
normal shell environment of the postgres user versus the environment
set up by "service" ... but it's not clear yet what that difference
is.
Also, it's not very clear whether you're trying to use the Red Hat/CentOS
packaging of PG, or the PGDG packaging. As Adrian alluded to, those are
not terribly compatible --- if you've got fragments of both laying about,
that could be causing issues.
regards, tom lane
Attachment:
postgresql-9.2
Description: Binary data
