| From: | Brian Dunavant <brian(at)omniti(dot)com> |
|---|---|
| To: | Thomas Kellerer <spam_eater(at)gmx(dot)net> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: date with month and year |
| Date: | 2015-05-21 21:35:27 |
| Message-ID: | CAJTy2e=EzT7Ct7JSBN5V_7SZCfjT2GdEPsFsaev=22_LWXA0ZA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, May 21, 2015 at 5:27 PM, Thomas Kellerer <spam_eater(at)gmx(dot)net> wrote:
> Postgres does not store the time zone. When storing a timestamp with time
> zone, it
> is normalized to UTC based on the timezone of the client. When you retrieve
> it,
> it is adjusted to the time zone of the client.
>
Sorry, I misspoke. Thank you for correcting it. It is storing it as
UTC time zone. The rest of my post still applies. You will get the
wrong wall-clock time for the future date because it is stored as UTC
and the conversion rules will have changed giving you a different time
when you convert it back to the local time zone.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andy Chambers | 2015-05-21 21:41:21 | Re: Unit tests and foreign key constraints |
| Previous Message | Paul Jungwirth | 2015-05-21 21:33:45 | Re: date with month and year |