On 10/02/2013 02:53 PM, Tim Uckun wrote:
I do think it would help to add it to the docs. The name "TIMESTAMP WITH
TIME ZONE" clearly implies the time zone is stored in the field. One
day there will really be a timestamp with time zone embedded in it field
and I wonder what they will call that.
I do think it would help to add it to the docs. The name "TIMESTAMP WITH
TIME ZONE" clearly implies the time zone is stored in the field. One day
there will really be a timestamp with time zone embedded in it field and I
wonder what they will call that.
On Wed, Oct 02, 2013 at 10:40:36AM -0700, Steve Crawford wrote:
> >>>The reason for that is that in PostgreSQL there is no time zone
> >>information stored along with a "timestamp with time zone",
> >>it is stored in UTC.
> >A better name might perhaps been "timezone aware timestamp".
> >
> >Karst
On 10/02/2013 01:49 AM, Tim Uckun wrote:
>The reason for that is that in PostgreSQL there is no time zone
information stored along with a "timestamp with time zone",
it is stored in UTC.
That seems unintuitive. What is the difference between timestamp
without time zone and timestamp with time z
On 10/02/2013 04:19 AM, Karsten Hilbert wrote:
On Wed, Oct 02, 2013 at 09:49:38PM +1300, Tim Uckun wrote:
The reason for that is that in PostgreSQL there is no time zone
information stored along with a "timestamp with time zone",
it is stored in UTC.
A better name might perhaps been "timezone
On 10/02/2013 05:58 AM, Karsten Hilbert wrote:
On Wed, Oct 02, 2013 at 11:48:02AM +, Albe Laurenz wrote:
Or does that still need some C sprinkling (for operator support, say) ?
Exactly. If you want "<" to work right for this data type
that's the road you have to go.
I see.
Whatever bec
On Wed, Oct 02, 2013 at 02:09:23PM +, Albe Laurenz wrote:
> Karsten Hilbert wrote:
> > Whatever became of the 2011 intent to implement
> > the above that's linked to in the blog post ?
>
> You'd have to ask Alvaro.
I figured he'd maybe read this on-list :-)
Karsten
--
GPG key ID E4071346 @
Karsten Hilbert wrote:
> Whatever became of the 2011 intent to implement
> the above that's linked to in the blog post ?
You'd have to ask Alvaro.
Yours,
Laurenz Albe
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresq
On Wed, Oct 02, 2013 at 11:48:02AM +, Albe Laurenz wrote:
>> Or does that still need some C sprinkling (for operator support, say) ?
>
> Exactly. If you want "<" to work right for this data type
> that's the road you have to go.
I see.
Whatever became of the 2011 intent to implement
the abo
Karsten Hilbert wrote:
> > > Maybe the question I need to ask is "how can I store the time zone along
> > > with the timestamp"
> >
> > Store an additional field "offset".
> > If you want to invest more energy and don't mind writing C,
> > you could create your own data type.
>
> Might not a comp
On Wed, Oct 02, 2013 at 09:18:30AM +, Albe Laurenz wrote:
> > Maybe the question I need to ask is "how can I store the time zone along
> > with the timestamp"
>
> Store an additional field "offset".
> If you want to invest more energy and don't mind writing C,
> you could create your own dat
On Wed, Oct 02, 2013 at 09:49:38PM +1300, Tim Uckun wrote:
> >The reason for that is that in PostgreSQL there is no time zone
> information stored along with a "timestamp with time zone",
> it is stored in UTC.
A better name might perhaps been "timezone aware timestamp".
Karsten
--
GPG key ID E
On Wed, Oct 02, 2013 at 09:49:38PM +1300, Tim Uckun wrote:
> Maybe the question I need to ask is "how can I store the time zone along
> with the timestamp"
You need an extra field, say, of type interval.
Karsten
--
GPG key ID E4071346 @ gpg-keyserver.de
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9
Tim Uckun wrote:
>> The reason for that is that in PostgreSQL there is no time zone
>> information stored along with a "timestamp with time zone",
>> it is stored in UTC.
>
> That seems unintuitive. What is the difference between timestamp without time
> zone and timestamp with
> time zone? I was
That's interesting article but it tells me that I can't really use the
timestamp with time zone data type. I really need to store the time zone
information along with the datetime and do not want to automatically
convert the timestamp to the connection time zone.
If one row has a timestamp in UT
On 02/10/2013, at 6:49 PM, Tim Uckun wrote:
> >The reason for that is that in PostgreSQL there is no time zone
> information stored along with a "timestamp with time zone",
> it is stored in UTC.
>
> That seems unintuitive. What is the difference between timestamp without time
> zone and times
>The reason for that is that in PostgreSQL there is no time zone
information stored along with a "timestamp with time zone",
it is stored in UTC.
That seems unintuitive. What is the difference between timestamp without
time zone and timestamp with time zone? I was expecting to have the time
zone s
Tim Uckun wrote:
> I have the following query.
[...]
> SELECT
> interval_start,
> (interval_start AT TIME ZONE 'Africa/Monrovia')::timestamp with time zone as
> interval_start_in_africa,
> min_datetime,
> min_datetime AT TIME ZONE 'Europe/Berlin' as min_datetime_in_berlin,
> max_datetime,
I have the following query.
with parsed_data as (
SELECT
devicereportedtime ,
DATE_TRUNC('minute', devicereportedtime - (EXTRACT(minute FROM
devicereportedtime)::integer % 5 || 'minutes')::interval) as interval_start
FROM systemevents
WHERE devicereportedtime >=
19 matches
Mail list logo
