Brian Dunavant wrote on 21.05.2015 21:51:
> It's probably worth noting that both the Ruby 'best practice' AND
> Postgres have a failure case when dealing with future dates precisely
> because they are storing the data as UTC with a time zone. This is
> one case where storing the data WITHOUT TIME ZONE would actually save
> your bacon.
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.