Re: LOCALTIMESTAMP has wrong time zone - Mailing list pgsql-bugs

From Jonathan Brinkman
Subject Re: LOCALTIMESTAMP has wrong time zone
Date
Msg-id 000a01cbd473$9f317fe0$dd947fa0$@com
Whole thread Raw
In response to Re: LOCALTIMESTAMP has wrong time zone  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List pgsql-bugs
Well, here is the CREATE TABLE if that's what you mean:

CREATE TABLE "clientdata"."general_comments" (
  "commentid" INTEGER DEFAULT nextval('general_comments_seq'::regclass) NOT
NULL,
  "commentvalue" VARCHAR(255) NOT NULL,
  "personid" INTEGER,
  "userid" INTEGER NOT NULL,
  "commentdatetime" TIMESTAMP WITHOUT TIME ZONE DEFAULT
timezone('EST'::text, now()) NOT NULL,
  "createddatetime" TIMESTAMP(0) WITHOUT TIME ZONE DEFAULT now(),
  "createddatetime2" TIMESTAMP(0) WITHOUT TIME ZONE DEFAULT
'now'::text::timestamp without time zone,
  CONSTRAINT "pk_general_comments_commentid" PRIMARY KEY("commentid"),
) WITH OIDS;


-----Original Message-----
From: Kevin Grittner [mailto:Kevin.Grittner@wicourts.gov]
Sent: Thursday, February 24, 2011 5:06 PM
To: JB@BlackSkyTech.com; pgsql-bugs@postgresql.org
Subject: Re: [BUGS] LOCALTIMESTAMP has wrong time zone

"Jonathan Brinkman" <JB@BlackSkyTech.com> wrote:

> My default timestamps in my database all are +5 hours in the future

Can you copy paste actual statements and results?

-Kevin

pgsql-bugs by date:

Previous
From: "Jonathan Brinkman"
Date:
Subject: Re: LOCALTIMESTAMP has wrong time zone
Next
From: Greg Stark
Date:
Subject: Re: Function trunc() behaves in unexpected manner with different data types