| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | <mtweber(at)gmail(dot)com> |
| Cc: | <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: Proposal for better support of time-varying timezone abbreviations |
| Date: | 2014-10-07 16:48:34 |
| Message-ID: | 54341962.7030202@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 10/6/14, 6:19 PM, Jim Nasby wrote:
> FWIW, I agree for timestamptz, but I do wish we had a timestamp datatype that stored the exact timezone in effect when the data was entered. That can really, REALLY save your rear if you screw up either timezone in postgresql.conf, or the server's timezone. The part that seems hard (at least to me) is the question of how to actually store the timezone, because I don't think storing the text string "America/Central" is going to cut it. :/
For the archives... there's an extension that does what I'd been talking about: http://pgxn.org/dist/timestampandtz/.
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2014-10-07 16:53:30 | Re: OCLASS_ROWSECURITY oversights, and other kvetching |
| Previous Message | Fabrízio de Royes Mello | 2014-10-07 16:44:09 | Re: pgaudit - an auditing extension for PostgreSQL |