| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Treat <rob(at)xzilla(dot)net> |
| Cc: | Álvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, bristleconeweb(at)gmail(dot)com, pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: timestamp with time zone ~> GMT |
| Date: | 2025-02-06 22:33:47 |
| Message-ID: | 1209685.1738881227@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
Robert Treat <rob(at)xzilla(dot)net> writes:
> On Mon, Feb 3, 2025 at 12:23 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Hmm, I kind of like the up-front statement that timestamptz stores
>> UTC. How about this simpler change?
> I thought the re-order made sense since the preceding paragraph talks
> exclusively about behavior, so this paragraph first contrasts the
> behavioral difference between the two, and then mentions the storage
> aspects as part of that story.
> I actually like the above as well, but if it were me I'd move all
> mentions of storage (the existing + the above) to the end of the
> paragraph after the behavior aspects.
OK, it makes more sense when considering the previous para as well.
Here's a combined proposal that also adds glossary entries.
regards, tom lane
| Attachment | Content-Type | Size |
|---|---|---|
| v2-0001-Clarify-timestamptz-input-time-zone-behavior.patch | text/x-diff | 2.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Doc comments form | 2025-02-07 10:43:58 | Regarding explanation to store and retrieve postgres geometric features |
| Previous Message | Robert Treat | 2025-02-06 21:21:51 | Re: Minor suggestions for docs regarding json_table |