Commit 0d9819f
committed
Measure epoch of timestamp-without-time-zone from local not UTC midnight.
This patch reverts commit 191ef2b
and thereby restores the pre-7.3 behavior of EXTRACT(EPOCH FROM
timestamp-without-tz). Per discussion, the more recent behavior was
misguided on a couple of grounds: it makes it hard to get a
non-timezone-aware epoch value for a timestamp, and it makes this one
case dependent on the value of the timezone GUC, which is incompatible
with having timestamp_part() labeled as immutable.
The other behavior is still available (in all releases) by explicitly
casting the timestamp to timestamp with time zone before applying EXTRACT.
This will need to be called out as an incompatible change in the 9.2
release notes. Although having mutable behavior in a function marked
immutable is clearly a bug, we're not going to back-patch such a change.1 parent 442da68 commit 0d9819f
2 files changed
+6
-23
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
6684 | 6684 | | |
6685 | 6685 | | |
6686 | 6686 | | |
6687 | | - | |
| 6687 | + | |
6688 | 6688 | | |
| 6689 | + | |
| 6690 | + | |
6689 | 6691 | | |
6690 | 6692 | | |
6691 | 6693 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
4066 | 4066 | | |
4067 | 4067 | | |
4068 | 4068 | | |
4069 | | - | |
4070 | | - | |
4071 | | - | |
4072 | | - | |
4073 | | - | |
4074 | | - | |
4075 | | - | |
4076 | | - | |
4077 | | - | |
4078 | | - | |
4079 | | - | |
4080 | | - | |
4081 | | - | |
4082 | | - | |
4083 | | - | |
4084 | | - | |
4085 | | - | |
4086 | | - | |
4087 | | - | |
4088 | 4069 | | |
4089 | | - | |
| 4070 | + | |
4090 | 4071 | | |
4091 | | - | |
| 4072 | + | |
4092 | 4073 | | |
4093 | 4074 | | |
4094 | | - | |
| 4075 | + | |
4095 | 4076 | | |
4096 | 4077 | | |
4097 | 4078 | | |
| |||
0 commit comments