From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Chuck Martin <clmartin(at)theombudsman(dot)com> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Column type changed "spontanously"? |
Date: | 2019-05-09 13:33:41 |
Message-ID: | CAKFQuwZqh2v5nzj4Nnp6+7YePrSgj-QYDQu=9-5HEP2y0tGbVw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thursday, May 9, 2019, Chuck Martin <clmartin(at)theombudsman(dot)com> wrote:
> I have several columns that were created as "timestamp without time zone",
> but I changed them in 2014 to "timestamp with time zone". Recently, when I
> got notified that times had suddenly changed, I checked and found the
> columns had reverted to "timestamp without time zone." This seems
> impossible, yet it seems to have happened. Any ideas on what could cause
> this? My application has the privileges to do this, as it changed the data
> type to support time zones. But there is no code that could change it back
> not to support time zones.
>
No clue
>
> The database in on
>
> "PostgreSQL 9.3.1 on x86_64-unknown-linux-gnu, compiled by gcc (GCC) 4.4.7
> 20120313 (Red Hat 4.4.7-3), 64-bit"
>
Given the issues with the early 9.3 releases running 9.3.1 is a extremely
unwise decision. Beyond the unwise-ness of not keeping up with minor
releases generally.
> What other information would help solve this?
>
Log files containing DDL commands
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2019-05-09 13:33:49 | Re: Column type changed "spontanously"? |
Previous Message | Chuck Martin | 2019-05-09 13:14:35 | Column type changed "spontanously"? |