| From: | Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Timestamp with vs without time zone. |
| Date: | 2021-09-22 15:41:30 |
| Message-ID: | YUtOqhWiCXbiqvr7@hermes.hilbert.loc |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Am Wed, Sep 22, 2021 at 08:11:50PM +1200 schrieb Tim Uckun:
> A korean user will fetch you single page app as static HTML from S3
> with cloudfront. It will hit your japanese API server, which will
> fetch the data from your japanese read only replica with the master
> being in Australia.
>
> The master DB writes the records has to know your end user is in
> Korea somehow so you have to carry that time zone all the way across
> those tiers.
One does not: as soon as the real-world concept of
point-in-time hits the machine it gets converted to UTC. When
it leaves the machine (towards user consumption) it gets
converted to whatever is desired.
UTC = UTF8
Karsten
--
GPG 40BE 5B0E C98E 1713 AFA6 5BC0 3BEA AC80 7D4F C89B
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Lewis | 2021-09-22 15:56:24 | Re: Timestamp with vs without time zone. |
| Previous Message | Michael Lewis | 2021-09-22 14:11:15 | Re: Question about behavior of conditional indexes |