On Tue, 21 Sept 2021 at 13:40, Peter J. Holzer <hjp-pgsql@xxxxxx> wrote:
On 2021-09-21 13:34:21 -0400, Dave Cramer wrote:
> On Tue, 21 Sept 2021 at 13:20, Peter J. Holzer <hjp-pgsql@xxxxxx> wrote:
> On 2021-09-21 20:50:44 +1200, Tim Uckun wrote:
> > It's just that the phrase "timestamp with time zone" would seem to
> > indicate the time zone is stored somewhere in there.
>
> I absolutely agree. Calling a type which doesn't include a timezone
> "timestamp with timezone" is - how do I put this? - more than just
> weird. "timestamp without timezone" should be called "local timestamp
> with unspecified timezone" and "timestamp with timezone" should be
> called "global timestamp without timezone". However, those aren't SQL
> names.
>
>
>
> I would say this is a perspective thing. It's a timestamp with a time
> zone from the client's perspective.
I disagree. When I read back the value the original timezone is lost. So
it clearly DOESN'T store the timestamp WITH the timezone.
I never said it stored the timezone. I said that it has a timezone.
Dave Cramer
www.postgres.rocks
