| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Thomas Kellerer <spam_eater(at)gmx(dot)net> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: When exactly is a TIMESTAMPTZ converted to the sessions time zone? |
| Date: | 2018-07-03 21:00:17 |
| Message-ID: | 65821.1530651617@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Thomas Kellerer <spam_eater(at)gmx(dot)net> writes:
> A recent discussion around timestamptz behaviour has lead me to question my own understanding on how a TIMESTAMPTZ is converted to the session's time zone.
> I assumed this conversion happens *on the server* before the value is sent to the client.
It's done in the datatype's output conversion function.
> A co-worker of mine claims that this is purely a client side thing, and that the server will always send the "plain" UTC value that is stored in a timestamptz column.
Your co-worker is certainly wrong so far as text output is concerned.
If you retrieve data in binary format, though, it looks like you get
the raw (un-rotated) timestamp value, so that any conversion would have
to be done on the client side.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tim Cross | 2018-07-03 22:13:28 | Re: FK v.s unique indexes |
| Previous Message | Thomas Kellerer | 2018-07-03 20:55:51 | When exactly is a TIMESTAMPTZ converted to the sessions time zone? |