From: | Bhushan Pathak <bhushan(dot)pathak02(at)gmail(dot)com> |
---|---|
To: | Devrim Gündüz <devrim(at)gunduz(dot)org> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: PostgreSQL 9.2.4 + CentOS 6.5 64 bit - segfault error in initdb |
Date: | 2014-06-09 11:02:45 |
Message-ID: | CAHJHQJ4H7gUQfSWwP89pupTzU3jLB3pQjxBz9dqY_nSGXWM-Dw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Trying to figure out shell environment differences between the service
script & postgres shell, if I comment out the following variable in profile
file/add them after performing initdb operation, the postgresql operations
seem to work fine -
PATH=$PATH:/usr/pgsql-9.2/bin
export PATH
export POSTGRESQL_JDBC_DRIVER=/opt/lib/postgresql-9.2-1003.jdbc4.jar
export PG_HOME=/var/lib/pgsql/data/
These variables are needed by a few cron scripts that would be installed
later on after my postgres config completes successfully.
The yum postgresql link I used earlier to download the RPM dos not the
debuginfo package for 9.2.4 version. Will it be OK to use the latest
debuginfo package with the rest being on version 9.2.4? Or I will have to
use all the latest RPM packages?
Thanks
Bhushan Pathak
On Mon, Jun 9, 2014 at 3:34 PM, Devrim Gündüz <devrim(at)gunduz(dot)org> wrote:
>
> Hi,
>
> On Mon, 2014-06-09 at 14:23 +0530, Bhushan Pathak wrote:
> > A core file was not generated.
>
> Can you please also install the -debuginfo package?
>
> Regards,
>
> --
> Devrim GÜNDÜZ
> Principal Systems Engineer @ EnterpriseDB: http://www.enterprisedb.com
> PostgreSQL Danışmanı/Consultant, Red Hat Certified Engineer
> Twitter: @DevrimGunduz , @DevrimGunduzTR
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Khangelani Gama | 2014-06-09 11:41:30 | pg_standby replication problem |
Previous Message | Devrim Gündüz | 2014-06-09 10:04:37 | Re: PostgreSQL 9.2.4 + CentOS 6.5 64 bit - segfault error in initdb |