Re: BUG #2882: jdbc driver: date returned from a stored proc is incorrect

Поиск
Список
Период
Сортировка
От Ravi Periasamy
Тема Re: BUG #2882: jdbc driver: date returned from a stored proc is incorrect
Дата
Msg-id 484416.40076.qm@web60523.mail.yahoo.com
обсуждение исходный текст
Ответ на Re: BUG #2882: jdbc driver: date returned from a stored proc is incorrect  (Alvaro Herrera <alvherre@commandprompt.com>)
Список pgsql-bugs
I do not think this is a server issue, seems like a
driver issue. When I connect to the DB from RHEL4
through the driver (running on RHEL4) it works. But,
when the driver is running on RHEL3 it fails.

Anyways, here's the output:

[root@bdc31014e pgsql]# pg_controldata `pwd`/data
pg_control version number:            812
Catalog version number:               200510211
Database system identifier:
4972362701494942605
Database cluster state:               in production
pg_control last modified:             Thu 11 Jan 2007
04:32:27 AM IST
Current log file ID:                  0
Next log file segment:                2
Latest checkpoint location:           0/15F3CD0
Prior checkpoint location:            0/15F3B1C
Latest checkpoint's REDO location:    0/15F3CD0
Latest checkpoint's UNDO location:    0/0
Latest checkpoint's TimeLineID:       1
Latest checkpoint's NextXID:          5195
Latest checkpoint's NextOID:          25214
Latest checkpoint's NextMultiXactId:  1
Latest checkpoint's NextMultiOffset:  0
Time of latest checkpoint:            Thu 11 Jan 2007
04:32:27 AM IST
Maximum data alignment:               4
Database block size:                  8192
Blocks per segment of large relation: 131072
Bytes per WAL segment:                16777216
Maximum length of identifiers:        64
Maximum columns in an index:          32
Date/time type storage:               floating-point
numbers
Maximum length of locale name:        128
LC_COLLATE:                           en_US.UTF-8
LC_CTYPE:                             en_US.UTF-8
[root@bdc31014e pgsql]#


What is IIRC?

Thanks
Ravi

--- Alvaro Herrera <alvherre@commandprompt.com> wrote:

> Ravi wrote:
>
> > On Red Hat Enterprise Linux AS release 4 (Nahant
> Update 3) the milliseconds
> > returned is as follows
> >
> > -2209028400000 =
> -25567.458333333333333333333333333 = Jan 1 1900
> >
> > On Red Hat Enterprise Linux AS release 3 (Taroon
> Update 3) the milliseconds
> > returned is as follows
> > -2208952800000 =
> -25566.583333333333333333333333333 = Jan 2 1900
>
> Is one of these compiled with
> --enable-integer-datetimes, and the other
> not?  You can tell by calling pg_controldata, IIRC.
>
> --
> Alvaro Herrera
> http://www.CommandPrompt.com/
> PostgreSQL Replication, Consulting, Custom
> Development, 24x7 support
>




____________________________________________________________________________________
Need a quick answer? Get one in minutes from people who know.
Ask your question on www.Answers.yahoo.com

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

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: BUG #2882: jdbc driver: date returned from a stored proc is incorrect
Следующее
От: "Ismail Cansiz"
Дата:
Сообщение: BUG #2884: Bug in rs.getInt(colname) when JMV language is Turkish