Tom Lane wrote:
Ericson Smith <[EMAIL PROTECTED]> writes:I realized I made a mistake in that initial email (should have said 12am instead of pm). However, I tried:
When using date oriented functions on Postgresql, the time is an hour off, or in certain times, one hour ahead.
System Timezone: EST
System Time (date command): Thu Aug 26 09:44:28 EDT 2004
SELECT now(); : 2004-08-26 08:44:31.307343-05
SELECT date_part('epoch', '2004-08-26'::timestamp) ; : 1093496400 (1am on that day -- should be 12pm)
Looks exactly right to me. 1093496400 corresponds to 1AM EDT, or midnight EST, and after all you do have the timezone set to EST. Possibly you want the zone set to EST5EDT instead.
regards, tom lane
> set local time zone 'EST5EDT'; SET > select now(); now ------------------------------- 2004-08-26 10:17:45.472901-05
[EMAIL PROTECTED] data]# date Thu Aug 26 11:21:01 EDT 2004
- Ericson
begin:vcard fn:Ericson Smith n:Smith;Ericson org:Did-it.com;Programming adr:#304;;55 Maple Avenue;Rockville Center;NY;11570;USA email;internet:[EMAIL PROTECTED] title:Web Developer tel;work:516-255-0500 tel;cell:646-483-3420 note:Nothing special! x-mozilla-html:FALSE url:http://www.did-it.com version:2.1 end:vcard
---------------------------(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