Thread: BUG #14182: Wrong time stamp exactly at 1996 hour 3

VGhlIGZvbGxvd2luZyBidWcgaGFzIGJlZW4gbG9nZ2VkIG9uIHRoZSB3ZWJz
aXRlOgoKQnVnIHJlZmVyZW5jZTogICAgICAxNDE4MgpMb2dnZWQgYnk6ICAg
ICAgICAgIE9sbW8gWmF2YWxhCkVtYWlsIGFkZHJlc3M6ICAgICAgb2xtb3ph
dmFsYUBnbWFpbC5jb20KUG9zdGdyZVNRTCB2ZXJzaW9uOiA5LjQuNgpPcGVy
YXRpbmcgc3lzdGVtOiAgIFVidW50dSAxNi4wNApEZXNjcmlwdGlvbjogICAg
ICAgIAoKSWYgeW91IGNyZWF0ZSBhIHRhYmxlIHdpdGgganVzdCBpZCBhbmQg
bXlkYXRlICh0aW1lc3RhbXAgd2l0aG91dCB6b25lKSBhbmQKdGhlbiB5b3Ug
ZXhlY3V0ZToNCg0KSU5TRVJUIElOVE8gdGVzdCAoZmVjaGEpIFZBTFVFUwoo
dG9fdGltZXN0YW1wKCcwNy8wNC8xOTk2LzInLCdERC9NTS9ZWS9ISDI0Jykp
DQpJTlNFUlQgSU5UTyB0ZXN0IChmZWNoYSkgVkFMVUVTCih0b190aW1lc3Rh
bXAoJzA3LzA0LzE5OTYvMycsJ0REL01NL1lZL0hIMjQnKSkNCg0KSXQgc2hv
dWxkIGdpdmUgeW91IHR3byBkaWZmZXJlbnQgaG91cnMsIGJ1dCBpdCB3aWxs
IGdpdmUgeW91IHRoZSBzYW1lIGhvdXIuCkkgd2FzIGZpbGxpbmcgYSB2ZXJ5
IGxhcmdlIGRhdGFiYXNlIGFuZCB0aGlzIHByb2JsZW0gc2VlbXMgdG8gYXBw
ZWFyIG9ubHkgYXQKdGhpcyBzcGVjaWZpYyBkYXRlIGFuZCB0aW1lLiAKCg==

On 6/8/2016 1:37 PM, olmozavala@gmail.com wrote:
> If you create a table with just id and mydate (timestamp without zone) and
> then you execute:
>
> INSERT INTO test (fecha) VALUES
> (to_timestamp('07/04/1996/2','DD/MM/YY/HH24'))
> INSERT INTO test (fecha) VALUES
> (to_timestamp('07/04/1996/3','DD/MM/YY/HH24'))
>
> It should give you two different hours, but it will give you the same hour.
> I was filling a very large database and this problem seems to appear only at
> this specific date and time.

that date/time is exactly when DST began that year in the USA... The
function to_timestamp returns a timestamptz (timestamp with time zone).

--
john r pierce, recycling bits in santa cruz

On 6/8/2016 2:48 PM, Olmo Zavala Romero wrote:
> Is there a function that do not take into account the time zone?
> I have defined my variable as "timestamp WITHOUT TIME ZONE" and my
> original data do NOT have DST so how can I add this into my database.

set your client timezone to UTC


--
john r pierce, recycling bits in santa cruz