From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Chuck Martin <clmartin(at)theombudsman(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Column type changed "spontanously"? |
Date: | 2019-05-09 13:33:49 |
Message-ID: | a4b84204-627d-e514-0b7f-e346cd886eaf@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 5/9/19 6:14 AM, Chuck Martin 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.
>
> 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"
>
> What other information would help solve this?
Assuming you have log_statement set to ddl or higher and the logs still
exist I would look in them for an ALTER TABLE ... statement on that column.
>
> Chuck Martin
> Avondale Software
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2019-05-09 13:39:57 | Re: perl path issue |
Previous Message | David G. Johnston | 2019-05-09 13:33:41 | Re: Column type changed "spontanously"? |