From: | Marko Tiikkaja <marko(at)joh(dot)to> |
---|---|
To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | to_char_at_timezone()? |
Date: | 2014-11-04 23:48:57 |
Message-ID: | 545965E9.3010403@joh.to |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
9.4 FINALLY added the UTC offset formatting pattern to to_char().
However, it falls a bit short in the sense that it's always the time
zone offset according to the effective TimeZone value. This has a few
issues as far as I can tell:
1) It's not truly controlled by the query which produces the
timestamptz values in the case of e.g. functions
2) Having to SET LOCAL before a query is quite ugly
3) It supports only a single TimeZone value per query
So I got into thinking whether it would make sense to provide a new
function, say, to_char_at_timezone() to solve this problem. For example:
local:marko=#* select now();
now
-------------------------------
2014-11-05 00:43:47.954662+01
(1 row)
local:marko=#* select to_char_at_timezone(now(), 'YYYY-MM-DD
HH24:MI:SSOF', 'Etc/Utc');
to_char_at_timezone
------------------------
2014-11-04 23:43:47+00
(1 row)
local:marko=#* select to_char_at_timezone(now(), 'YYYY-MM-DD
HH24:MI:SSOF', 'America/Los_Angeles');
to_char_at_timezone
------------------------
2014-11-04 15:43:47-08
(1 row)
Any thoughts? The patch is quite trivial.
.marko
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2014-11-04 23:57:07 | Re: tracking commit timestamps |
Previous Message | Tom Lane | 2014-11-04 23:48:14 | Re: ltree::text not immutable? |