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

TIMESTAMP('now') y2k bug

From: "Dan Linderman" <linderdm(at)ironhilltechnology(dot)com>
To: <pgsql-bugs(at)postgresql(dot)org>
Subject: TIMESTAMP('now') y2k bug
Date: 2000-01-06 19:35:48
Message-ID: 003201bf587d$3c202880$e68ca8c0@eng.ironhilltech.com (view raw or flat)
Thread:
Lists: pgsql-bugs
Your name  : Dan Linderman
Your email address : linderdm(at)ironhilltech(dot)com


System Configuration
---------------------
  Architecture (example: Intel Pentium)   : Intel Pentium III 500mhz

  Operating System (example: Linux 2.0.26 ELF)  : Redhat LINUX 6.0

  PostgreSQL version (example: PostgreSQL-6.5.3):   PostgreSQL-6.5.3

  Compiler used (example:  gcc 2.8.0)  : ?


Please enter a FULL description of your problem:
------------------------------------------------
When I insert a timestamp using the TIMESTAMP('now') into a date field,
"1999-12-31 19:00:00-05" is what is inserted into the field.  This has been
done on multiple machines with PostgreSQL-6.5.3, and has been used when
inserting into a timestamp field, and a datetime field.




Please describe a way to repeat the problem.   Please try to provide a
concise reproducible example, if at all possible:
----------------------------------------------------------------------
Create a table with a date field.  Insert TIMESTAMP('now') into that field.
Select that row to see bug.



Dan Linderman
Web Programmer
Iron Hill Technology
linderdm(at)ironhilltech(dot)com
302-369-9750 x23
www.ironhilltech.com


pgsql-bugs by date

Next:From: Culberson, PhilipDate: 2000-01-06 20:58:21
Subject: RE: [GENERAL] Benchmarks
Previous:From: Tom LaneDate: 2000-01-06 19:03:55
Subject: Re: [BUGS] problem creating index in 6,5,3

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