On Fri, Jan 10, 2014 at 10:06 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
>
> However, I suspect that the key reason this isn't working is SELinux
>
> Tom, I hate to say it - but I just cried out of happiness.
Thank you for your help. SELinux was causing the issue (I did not suspect
it as I usually get pop-ups when there is a violation). setting selinux to
permission allowed the database to start up - so that now tells me where my
issue lies.
Thank you again - I really do appreciate it.