On Fri, Mar 11, 2011 at 9:31 AM, Bruce Momjian wrote:
> Robert Haas wrote:
>> On Thu, Mar 10, 2011 at 10:37 PM, Bruce Momjian wrote:
>> > Robert Haas wrote:
>> >> On Thu, Mar 10, 2011 at 4:08 PM, Bruce Momjian wrote:
>> >> > Was this fixed?
>> >>
>> >> Not yet. ?I can probably fix it, if nobody
"Kevin Grittner" writes:
> "Jonathan Brinkman" wrote:
>> I guess EST is not DST-friendly?
> EST stands for Eastern *Standard* Time, which is explicitly *not*
> under Daylight Saving Time.
Right. SET TIMEZONE 'EST' gets you GMT-5 all year round.
For background see this bit in src/timezone/data
"Jonathan Brinkman" wrote:
> I guess EST is not DST-friendly?
EST stands for Eastern *Standard* Time, which is explicitly *not*
under Daylight Saving Time.
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
When in a command prompt I log into psql with merely "psql" and get
postgres=#, and run SELECT now(); I get the correct time.
When I log into my application's database with psql beta_cms_gate and get
beta_cms_gate=# prompt, and run SELECT now(); I get incorrect time (still
-05 timezone, and 1 hour
"Jonathan Brinkman" writes:
> My TO_CHAR function is now an hour off thanks to Daylight Savings Time.
> The dates are correct (I'm in EST: TZ=-04) but my function now returns TIME
> an hour early.
> (prior to DST we were TZ=-05).
> TIMESTAMPTZ data (v_dt): 2011-03-17 18:21:50-04
> FUNCTION SNIPP
My TO_CHAR function is now an hour off thanks to Daylight Savings Time.
The dates are correct (I'm in EST: TZ=-04) but my function now returns TIME
an hour early.
(prior to DST we were TZ=-05).
TIMESTAMPTZ data (v_dt): 2011-03-17 18:21:50-04
FUNCTION SNIPPET: to_char(v_dt, 'mm/dd/ hh:mi AM')
postgres=# set timezone='+03';
SET
postgres=# select now();
now
---
2011-03-18 11:20:29.696671+03
(1 row)
postgres=# set timezone='+03:00';
SET
postgres=# select now();
now
--
2011-03-18 05:20:35.46008-03
(1 row)
