Re: how to install postgres 8.0.4 in RHEL4

From: Devrim GUNDUZ <devrim(at)gunduz(dot)org>
To: venki <venkat_kurva(at)yahoo(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: how to install postgres 8.0.4 in RHEL4
Date: 2005-11-04 15:25:02
Message-ID: Pine.LNX.4.63.0511041722310.29452@mail.kivi.com.tr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


Hi,

On Fri, 4 Nov 2005, venki wrote:

> hello sir
> i have facing a problem past one weeks onwords
> iam using redhat enterprise linux 4 in that postgres version is 7.4
> i want to upgrade postgres version of the existing operating system RHEL4
> iam searched a lot of links but fail to get the result
> in the operating system rpm -qa | grep postgres
> <it is showing
> postres contrib 7.4
> ,, server
> ,, libs
> ,, docs
> ,, test
> ,, jdbc
> ,, p1
> ,, python
> ,, devel
> all above are the same version of postgres = 7.4
> could you tell me how to upgrade 8.0.* in RHEL4

(This is offtopic for this list).

Anyway, RHEL 4 will not provide PostgreSQL 8.0 in RHEL 4 (will do possibly
in RHEL 5). So, you should use the following binaries:

http://www.postgresql.org/ftp/binary/v8.0.4/linux/rpms/redhat/rhel-es-4/

to upgrade to 8.0. Please note that you'll need a dump/reload.

Regards,
--
Devrim GUNDUZ
Kivi Bilişim Teknolojileri - http://www.kivi.com.tr
devrim~gunduz.org, devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr
http://www.gunduz.org
>From pgsql-bugs-owner(at)postgresql(dot)org Fri Nov 4 15:43:03 2005
X-Original-To: pgsql-bugs-postgresql(dot)org(at)localhost(dot)postgresql(dot)org
Received: from localhost (av.hub.org [200.46.204.144])
by svr1.postgresql.org (Postfix) with ESMTP id 0BE72D99A4
for <pgsql-bugs-postgresql(dot)org(at)localhost(dot)postgresql(dot)org>; Fri, 4 Nov 2005 15:27:11 -0400 (AST)
Received: from svr1.postgresql.org ([200.46.204.71])
by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
with ESMTP id 43629-08
for <pgsql-bugs-postgresql(dot)org(at)localhost(dot)postgresql(dot)org>;
Fri, 4 Nov 2005 19:27:06 +0000 (GMT)
X-Greylist: delayed 01:08:14.080432 by SQLgrey-
Received: from svr2.postgresql.org (svr2.postgresql.org [65.19.161.25])
by svr1.postgresql.org (Postfix) with ESMTP id C965FD97FD
for <pgsql-bugs(at)postgresql(dot)org>; Fri, 4 Nov 2005 15:27:06 -0400 (AST)
Received: from mail.diuno.com.br (unknown [200.175.102.226])
by svr2.postgresql.org (Postfix) with ESMTP id 0CB9CF14A0
for <pgsql-bugs(at)postgresql(dot)org>; Fri, 4 Nov 2005 18:18:48 +0000 (GMT)
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01C5E16B.B7198A1F"
Subject: Missing seconds in a date (timestamp)
Date: Fri, 4 Nov 2005 16:15:47 -0200
Message-ID: <54CC7CADE26E884EB2BCEC863F5C1F70F9D25F(at)moscou(dot)diuno(dot)net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Missing seconds in a date (timestamp)
Thread-Index: AcXhZxGLQj+MysgISPyfJURuY3HLhwABImBg
From: =?iso-8859-1?Q?Eli=E9zer_Madeira_de_Campos?= <eliezer(at)diuno(dot)com(dot)br>
To: <pgsql-bugs(at)postgresql(dot)org>
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, score=0.001 required=5 tests=[HTML_MESSAGE=0.001]
X-Spam-Score: 0.001
X-Spam-Level:
X-Archive-Number: 200511/44
X-Sequence-Number: 13408

This is a multi-part message in MIME format.

------_=_NextPart_001_01C5E16B.B7198A1F
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hello everyone:
=20
I'm working to upgrade a database from PostgreSQL 7.3 to 8.0 version.
The database serves a complex J2EE application, running Jboss in =
multiple servers. All servers run Linux RedHat.
I found a problem yesterday.
Whenever the application inserts a date prior to 1914-01-01, the actual =
date written in the database is different. For instance:
'1900-01-01' is stored as '1899-12-31 23:59:32'. The column datatype is =
timestamp without timezone.
=20
If I run the command directly against the database (psql) the date is =
stored correctly. The weird thing is that we tried to debug the JDBC =
driver and it seems to be sending the correct information to the =
database.
=20
I couldn't find any report on this... so I guess it is most likely I'm =
doing something wrong.
=20
Any ideas?

Eli=E9zer Madeira de Campos
eliezer (at) diuno.com.br

------_=_NextPart_001_01C5E16B.B7198A1F
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2769" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft>
<DIV><FONT face=3DGeorgia color=3D#800000 size=3D2>Hello =
everyone:</FONT></DIV>
<DIV><FONT face=3DGeorgia color=3D#800000 size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DGeorgia color=3D#800000 size=3D2>I'm working to =
upgrade a database=20
from PostgreSQL 7.3 to 8.0 version.<BR>The database serves a complex =
J2EE=20
application, running Jboss in multiple servers. All servers run Linux=20
RedHat.<BR>I found a problem yesterday.<BR>Whenever the application =
inserts a=20
date prior to 1914-01-01, the actual date written in the database is =
different.=20
For instance:<BR>'1900-01-01' is stored as '1899-12-31 23:59:32'. The =
column=20
datatype is timestamp without timezone.</FONT></DIV>
<DIV><FONT face=3DGeorgia color=3D#800000 size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DGeorgia color=3D#800000 size=3D2>If I run the command =
directly=20
against the database (psql) the date is stored correctly. The weird =
thing is=20
that we tried to debug the JDBC driver and it seems to be sending the =
correct=20
information to the database.</FONT></DIV>
<DIV><FONT face=3DGeorgia color=3D#800000 size=3D2></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D896321418-04112005><FONT face=3DGeorgia =
color=3D#800000 size=3D2>I=20
couldn't find any report on this... so I guess it is most likely I'm =
doing=20
something wrong.</FONT></SPAN></DIV>
<DIV><SPAN class=3D896321418-04112005><FONT face=3DGeorgia =
color=3D#800000=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D896321418-04112005><FONT face=3DGeorgia =
color=3D#800000 size=3D2>Any=20
ideas?</FONT></SPAN></DIV>
<DIV><FONT face=3DGeorgia color=3D#800000 size=3D2></FONT><BR><FONT =
face=3DGeorgia=20
color=3D#800000 size=3D2>Eli=E9zer Madeira de Campos<BR>eliezer (at)=20
diuno.com.br<BR></FONT></DIV><FONT face=3DGeorgia=20
size=3D2></FONT></DIV></BODY></HTML>

------_=_NextPart_001_01C5E16B.B7198A1F--

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Eisentraut 2005-11-04 16:25:52 Re: Bad French support encoding for postgresql version 8.0.4
Previous Message Bernhard Weisshuhn 2005-11-04 12:42:22 Re: BUG #2019: tsearch2-related coredump