| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Nikita Glukhov <n(dot)gluhov(at)postgrespro(dot)ru>, pgsql-committers <pgsql-committers(at)lists(dot)postgresql(dot)org>, Alexander Korotkov <akorotkov(at)postgresql(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pgsql: Implement jsonpath .datetime() method |
| Date: | 2019-10-13 02:24:27 |
| Message-ID: | 31235.1570933467@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> writes:
> This patch also changes the way timestamp to timestamptz cast works.
> Previously it did timestamp2tm() then tm2timestamp(). Instead, after
> timestamp2tm() it calculates timezone offset and applies it to
> original timestamp value. I hope this is correct.
I'd wonder whether this gives the same answers near DST transitions,
where it's not real clear which offset applies.
Please *don't* wrap this sort of thing into an unrelated feature patch.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2019-10-13 08:54:19 | pgsql: Fix dependency handling of column drop with partitioned tables |
| Previous Message | Alexander Korotkov | 2019-10-13 01:52:21 | Re: pgsql: Implement jsonpath .datetime() method |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2019-10-13 02:51:45 | v12.0: reindex CONCURRENTLY: lock ShareUpdateExclusiveLock on object 14185/39327/0 is already held |
| Previous Message | Alexander Korotkov | 2019-10-13 01:52:21 | Re: pgsql: Implement jsonpath .datetime() method |