Re: Initdb error without much more details PostgreSQL 7.4.19

Поиск
Список
Период
Сортировка
От Laurent Barbier
Тема Re: Initdb error without much more details PostgreSQL 7.4.19
Дата
Msg-id BLU140-W41A962370853F8C95231A6A21C0@phx.gbl
обсуждение исходный текст
Ответ на Re: Initdb error without much more details PostgreSQL 7.4.19  (Tom Lane <tgl@sss.pgh.pa.us>)
Список 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,

--
Laurent

----------------------------------------
> To: barbierlaurent@hotmail.fr
> CC: pgsql-bugs@postgresql.org
> Subject: Re: [BUGS] Initdb error without much more details PostgreSQL 7.4=
.19=20
> Date: Thu, 21 Feb 2008 11:49:04 -0500
> From: tgl@sss.pgh.pa.us
>=20
> Laurent Barbier  writes:
>> I'm facing a trouble with the initdb execution of PostgreSQL 7.4.19 on a=
 Redhat 4 :
>=20
> Looks like SELinux problems to me.  Does it work after doing "setenforce =
0"?
>=20
>> 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
>=20
> 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.
>=20
>             regards, tom lane
>=20
> ---------------------------(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=E9n=E9ration. Cr=E9ez u=
n compte.=20
http://www.windowslive.fr/hotmail/default.asp

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: BUG #3951: SELECT ... WHERE Param = ? does not work if Param is of type bytea
Следующее
От: "Matthias Mohr"
Дата:
Сообщение: 8.3 problems with sspi authentication