Skip site navigation (1) Skip section navigation (2)

Re: Daylight Savings Time handling on persistent connections

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Randall Nortman <postgreslists(at)wonderclown(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Daylight Savings Time handling on persistent connections
Date: 2004-10-31 17:47:31
Message-ID: 28931.1099244851@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-general
Randall Nortman <postgreslists(at)wonderclown(dot)com> writes:
> I can't reproduce the error without messing up my clock, but from my
> logs, here's the text of the SQL sent to the server:

> insert into sensor_readings_numeric (sensor_id, reading_ts, reading,
> min, max) values (3, '2004-10-31 01:00:00', 0.540602, 0.519071837254,
> 0.551811824539)

> And this came back:
> ERROR:  duplicate key violates unique constraint "sensor_readings_numeric_pkey"

Hmm ... and you were generating that timestamp string how exactly?
I suspect that you actually sent the same timestamp string twice, one
hour apart, in which case I'd have to call this an application bug.
You really need to include the timezone specification in order to
have an unambiguous timestamp string.  It doesn't have to be UTC as you
previously suggested, but it does have to be labeled with the intended
zone.

			regards, tom lane

In response to

Responses

pgsql-general by date

Next:From: Randall NortmanDate: 2004-10-31 18:24:07
Subject: Re: Daylight Savings Time handling on persistent connections
Previous:From: Vinko VrsalovicDate: 2004-10-31 17:40:14
Subject: Re: Superuser log-in through a web interface?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group