Skip site navigation (1) Skip section navigation (2)

Re: Initdb error without much more details PostgreSQL 7.4.19

From: Laurent Barbier <barbierlaurent(at)hotmail(dot)fr>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Initdb error without much more details PostgreSQL 7.4.19
Date: 2008-02-21 19:06:43
Message-ID: BLU140-W41A962370853F8C95231A6A21C0@phx.gbl (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
Thanks a lot Tom,

It works without the security enhanced functionality ! So, I didn't try the Red Hat's RPMs.

Best regards,


> To: barbierlaurent(at)hotmail(dot)fr
> CC: pgsql-bugs(at)postgresql(dot)org
> Subject: Re: [BUGS] Initdb error without much more details PostgreSQL 7.4.19 
> Date: Thu, 21 Feb 2008 11:49:04 -0500
> From: tgl(at)sss(dot)pgh(dot)pa(dot)us
> Laurent Barbier  writes:
>> I'm facing a trouble with the initdb execution of PostgreSQL 7.4.19 on a Redhat 4 :
> Looks like SELinux problems to me.  Does it work after doing "setenforce 0"?
>> Then i install PostgreSQL binary in the order :
>> rpm -ivh  postgresql-libs-7.4.19-1PGDG.rhel4.i686.rpm
>> rpm -ivh postgresql-7.4.19-1PGDG.rhel4.i686.rpm
> You might try Red Hat's RPMs instead --- they contain fixes for some
> selinux issues, which AFAICT never got propagated into the PGDG RPMs.
> Also, make sure you are up to date with the latest selinux policy
> RPM.  Or you could just leave selinux turned off, but that might not
> be a great idea from a security standpoint.
> 			regards, tom lane
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
>        choose an index scan if your joining column's datatypes do not
>        match

Votre contact a choisi Hotmail, l'e-mail nouvelle génération. Créez un compte.

In response to

pgsql-bugs by date

Next:From: Andy SatoriDate: 2008-02-21 20:24:11
Subject: BUG #3978: plperl configure / build process behavior wrt Universal Binaries
Previous:From: Tom LaneDate: 2008-02-21 18:30:02
Subject: Re: BUG #3951: SELECT ... WHERE Param = ? does not work if Param is of type bytea

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group