| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Cc: | Keith Fiske <keith(at)omniti(dot)com>, PGSQL Mailing List <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Updating timezone setting |
| Date: | 2014-12-06 14:37:57 |
| Message-ID: | 20141206143757.GB28234@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Nov 10, 2014 at 05:09:10PM -0800, Adrian Klaver wrote:
> >Would there be any issues then just leaving the columns as "timestamp
> >without time zone"? I know that's not ideal, but that would be a big
> >project to try and convert every single one of those columns.
>
> The plus for converting is that timestamp with timezone anchors the
> time and you do not have to worry as much, about what the
> application is doing. That being said, I could see rolling that out
> over time:)
Sorry to be late on this, but since the data is already stored in GMT,
you might be able to just change the system catalogs to say timestamp
with time zone. I recommend you find a PG expert to research this and
test it.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2014-12-06 20:38:04 | Re: I did some testing of GIST/GIN vs BTree indexing… |
| Previous Message | David Johnston | 2014-12-06 03:33:26 | Fwd: Array Comparison |