| From: | Chapman Flack <chap(at)anastigmatix(dot)net> |
|---|---|
| To: | Dave Cramer <davecramer(at)gmail(dot)com>, Andres Freund <andres(dot)freund(at)enterprisedb(dot)com> |
| Cc: | David Fetter <david(at)fetter(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Binary support for pgoutput plugin |
| Date: | 2019-06-04 21:33:28 |
| Message-ID: | d645c3df-ff8e-140c-9b1e-f14602596842@anastigmatix.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 6/4/19 4:39 PM, Dave Cramer wrote:
> I haven't really thought this through completely but one place JDBC has
> problems with binary is with
> timestamps with timezone as we don't know which timezone to use. Is it safe
> to assume everything is in UTC
> since the server stores in UTC ?
PL/Java, when converting to the Java 8 java.time types (because those
are sane), will turn a timestamp with timezone into an OffsetDateTime
with explicit offset zero (UTC), no matter what timezone may have been
used when the value was input (as you've observed, there's no way to
recover that). In the return direction, if given an OffsetDateTime
with any nonzero offset, it will adjust the value to UTC for postgres.
So, yes, say I.
Regards,
-Chap
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2019-06-04 21:37:35 | Re: Sort support for macaddr8 |
| Previous Message | Tomas Vondra | 2019-06-04 21:30:03 | Re: Sort support for macaddr8 |