| From: | Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | Tim Uckun <timuckun(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Aw: Re: Timestamp with vs without time zone. |
| Date: | 2021-09-21 07:44:49 |
| Message-ID: | trinity-13c8aeec-e272-4fda-9aed-0e7aa37a561b-1632210289817@3c-app-gmx-bap35 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> > It seems like it would be so much more useful if the timestamp with
> > time zone type actually stored the time zone in the record.
>
> This has been requested before, and it would be closer to the intention
> of the SQL standard, but I guess it won't happen.
>
> For one, it would change on-disk storage, which would make it
> impossible to use pg_upgrade. It also would require timestamps to
> occupy more than 8 bytes.
>
> The best solution is probably to explicitly store the time zone as
> an additional column.
Would that not be a perfect candidate for a fully fleshed out,
exemplary composite type ?
(but, then, yes it would beg the question what the TZ field of
the composite is to actually mean...)
Karsten
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tim Uckun | 2021-09-21 08:02:01 | Re: Re: Timestamp with vs without time zone. |
| Previous Message | Karsten Hilbert | 2021-09-21 07:39:59 | Aw: Re: Timestamp with vs without time zone. |