Bug in function to_char() !!

[Najib Abi Fadel]

Hi, i am using PostgreSQL 7.3.2

there's a bug for the date '2005-03-27' !!!!!!!!!!!!!!! !!!!!!!!!!!!

SELECT to_char('2005-03-27'::date,'DD/MM/YYYY');
to_char
------------
26/03/2005
(1 row)

I get the date 26/03/2005 instead of 27/03/2005 !!!

For other dates the function works well !!

[Dirk Försterling]

Najib Abi Fadel wrote:

Hi, i am using PostgreSQL 7.3.2

there's a bug for the date '2005-03-27' !!!!!!!!!!!!!!! !!!!!!!!!!!!
I think you should replace or clean your keyboard. At least one key
seems to be sticky.
SELECT to_char('2005-03-27'::date,'DD/MM/YYYY');
to_char
------------
26/03/2005
(1 row)

No problem with 7.2.1 and 7.4.1. (don't have a 7.3.2 around).
Both work correctly:

dirk=> SELECT to_char('2005-03-27'::date,'DD/MM/YYYY');
to_char
------------
27/03/2005
(1 row)

--
D i r k F "o r s t e r l i n g
[e-mail] http://r.zorbla.de/
-------------
"A radioactive cat has eighteen half-lives."

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to ma*******@postg resql.org so that your
message can get through to the mailing list cleanly

[Karel Zak]

On Thu, Jul 01, 2004 at 09:47:38AM +0200, Najib Abi Fadel wrote:

Hi, i am using PostgreSQL 7.3.2

there's a bug for the date '2005-03-27' !!!!!!!!!!!!!!! !!!!!!!!!!!!

SELECT to_char('2005-03-27'::date,'DD/MM/YYYY');
to_char
------------
26/03/2005
(1 row)

I get the date 26/03/2005 instead of 27/03/2005 !!!

7.5devel:

# SELECT to_char('2005-03-27'::date,'DD/MM/YYYY');
to_char
------------
27/03/2005
The date looks like some date when is daylight saving time change,
maybe it's something already knows and fixed.

Can you check results of:

# SELECT '2005-03-27'::timestamp;
timestamp
---------------------
2005-03-27 00:00:00

# SHOW TIMEZONE;
TimeZone
---------------
Europe/Prague
Karel

--
Karel Zak <za***@zf.jcu.c z>
http://home.zf.jcu.cz/~zakkr/

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faqs/FAQ.html

[Stephane Bortzmeyer]

On Thu, Jul 01, 2004 at 09:53:34AM +0200,
Dirk Försterling <[e-mail]> wrote
a message of 33 lines which said:

No problem with 7.2.1 and 7.4.1. (don't have a 7.3.2 around).

7.3.4 seems OK so I assume the guy with the exclamation marks did not
type what he sent:

% psql template1
Welcome to psql 7.3.4, the PostgreSQL interactive terminal.

Type: \copyright for distribution terms
\h for help with SQL commands
\? for help on internal slash commands
\g or terminate with semicolon to execute query
\q to quit

template1=> SELECT to_char('2005-03-27'::date,'DD/MM/YYYY');
to_char
------------
27/03/2005
(1 row)
---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend

[Clodoaldo Pinto Neto]

[cpn@s00 work]$ rpm -q postgresql
postgresql-7.3.4-11

Fedora Core 1

KakaoStats=# SELECT
to_char('2005-03-27'::date,'DD/MM/YYYY');
to_char
------------
27/03/2005
(1 row)
--- Dirk_Försterlin g <[e-mail]> escreveu: > Najib
Abi Fadel wrote:

Hi, i am using PostgreSQL 7.3.2

there's a bug for the date '2005-03-27'

!!!!!!!!!!!!!!! !!!!!!!!!!!!

I think you should replace or clean your keyboard.
At least one key
seems to be sticky.

SELECT to_char('2005-03-27'::date,'DD/MM/YYYY');
to_char
------------
26/03/2005
(1 row)

No problem with 7.2.1 and 7.4.1. (don't have a 7.3.2
around).
Both work correctly:

dirk=> SELECT
to_char('2005-03-27'::date,'DD/MM/YYYY');
to_char
------------
27/03/2005
(1 row)

--
D i r k F "o r s t e r l i n g
[e-mail] http://r.zorbla.de/
-------------
"A radioactive cat has eighteen
half-lives."

---------------------------(end of
broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please
send an appropriate
subscribe-nomail command to
ma*******@postg resql.org so that your
message can get through to the mailing list
cleanly

_______________ _______________ _______________ _______________ __________

Yahoo! Mail - agora com 100MB de espaço, anti-spam e antivírus grátis!
http://br.info.mail.yahoo.com/

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

[Najib Abi Fadel]

I exactly typed what i sent.
Anyone with Postgresql 7.3.2 PLEASE try it and tell me what happens.

SELECT to_char('2005-03-27'::date,'DD/MM/YYYY');

7.3.4 seems OK so I assume the guy with the exclamation marks did not
type what he sent:

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faqs/FAQ.html

[Stefan Kaltenbrunner]

Najib Abi Fadel wrote:

I exactly typed what i sent.
Anyone with Postgresql 7.3.2 PLEASE try it and tell me what happens.

SELECT to_char('2005-03-27'::date,'DD/MM/YYYY');

template1=# select version();
version
------------------------------------------------------------------------
PostgreSQL 7.3.2 on i386-pc-linux-gnu, compiled by GCC gcc (GCC) 3.2.3
(1 row)

template1=# SELECT to_char('2005-03-27'::date,'DD/MM/YYYY');
to_char
------------
27/03/2005
(1 row)
Stefan

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

[Robin Ericsson]

On Thu, 2004-07-01 at 14:48, Stefan Kaltenbrunner wrote:

Najib Abi Fadel wrote:

I exactly typed what i sent.
Anyone with Postgresql 7.3.2 PLEASE try it and tell me what happens.

SELECT to_char('2005-03-27'::date,'DD/MM/YYYY');

template1=# select version();
version
------------------------------------------------------------------------
PostgreSQL 7.3.2 on i386-pc-linux-gnu, compiled by GCC gcc (GCC) 3.2.3
(1 row)

template1=# SELECT to_char('2005-03-27'::date,'DD/MM/YYYY');
to_char
------------
27/03/2005
(1 row)

I had the same problem in php due to DST, but that I guess depends on
the underlaying (buggy?) libc.

using 2005-03-27 12:00 instead of just 2005-03-27 solved the problem for
me.
regards,
Robin
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faqs/FAQ.html

[Tom Lane]

"Najib Abi Fadel" <na*******@usj. edu.lb> writes:

SELECT to_char('2005-03-27'::date,'DD/MM/YYYY');
to_char
------------
26/03/2005
(1 row)

What timezone setting are you using, and what kind of system is this on?
I suppose that day is a daylight-savings transition day for you, but no
one else is likely to reproduce the problem in a different zone ...

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to ma*******@postg resql.org so that your
message can get through to the mailing list cleanly

[Maciej Bliziñski]

Najib Abi Fadel wrote:

Hi, i am using PostgreSQL 7.3.2
there's a bug for the date '2005-03-27' !!!!!!!!!!!!!!! !!!!!!!!!!!!
For other dates the function works well !!

I have 7.4.2 and it works well:

maciej@matylda: ~$ psql template1
Welcome to psql 7.4.2, the PostgreSQL interactive terminal.

Type: \copyright for distribution terms
\h for help with SQL commands
\? for help on internal slash commands
\g or terminate with semicolon to execute query
\q to quit

template1=# SELECT to_char('2005-03-27'::date,'DD/MM/YYYY');
to_char
------------
27/03/2005
(1 row)

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match