On 06/18/2018 06:24 AM, Jeremy Finzel wrote:
On Fri, Jun 15, 2018 at 2:57 PM, Adrian Klaver
mailto:adrian.kla...@aklaver.com>> wrote:
On 06/15/2018 12:24 PM, Jeremy Finzel wrote:
Hello!
We often prefer to use timestamptz or "timestamp with time zone"
in our envi
On Fri, Jun 15, 2018 at 2:57 PM, Adrian Klaver
wrote:
> On 06/15/2018 12:24 PM, Jeremy Finzel wrote:
>
>> Hello!
>>
>> We often prefer to use timestamptz or "timestamp with time zone" in our
>> environment because of its actually storing "objective time" with respect
>> to UTC. But in my own wor
It is an unfortunate historical naming.
In these conversations I tell people to just always mentally translate
"timestamp with time zone" to "point in time". How it is stored internally
is entirely irrelevant except to the PostgreSQL developers and can
otherwise be ignored. All that matters is tha
On 06/15/2018 12:24 PM, Jeremy Finzel wrote:
Hello!
We often prefer to use timestamptz or "timestamp with time zone" in our
environment because of its actually storing "objective time" with
respect to UTC. But in my own work experience, I have scarcely
encountered a case where business users
Jeremy Finzel writes:
> We often prefer to use timestamptz or "timestamp with time zone" in our
> environment because of its actually storing "objective time" with respect
> to UTC. But in my own work experience, I have scarcely encountered a case
> where business users, and software engineers, d
On Fri, Jun 15, 2018 at 12:24 PM, Jeremy Finzel wrote:
> So it seems to me that "timestamp with time zone" is a misnomer in a big
> way, and perhaps it's worth at least clarifying the docs about this, or
> even renaming the type or providing an aliased type that means the same
> thing, something
