Re: COPY and custom datestyles. Or some other technique? - Mailing list pgsql-general

From Ron
Subject Re: COPY and custom datestyles. Or some other technique?
Date
Msg-id e38d14b4-7868-d42c-ff43-15f704e60e29@gmail.com
Whole thread Raw
In response to Re: COPY and custom datestyles. Or some other technique?  (Adrian Klaver <adrian.klaver@aklaver.com>)
Responses Re: COPY and custom datestyles. Or some other technique?  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-general
On 3/29/23 18:31, Adrian Klaver wrote:
> On 3/29/23 16:24, Ron wrote:
>> Postgresql 13.10
>>
>> $ psql -h myhost.example.com -X dba \
>>          -c "\copy ${tbl} from '/var/lib/pgsql/Rdb/${tbl}.csv' WITH 
>> DELIMITER '|';"
>> ERROR:  date/time field value out of range: "2013061914122501"
>> CONTEXT:  COPY t_id_master, line 1, column update_timestamp: 
>> "2013061914122501"
>>
>> The timestamp format generated by a legacy dbms is YYYYMMDDHHmmSSCC (year 
>> to centisecond, with no delimiters).
>>
>> Is there any way to convince Postgresql to import these fields?
>
> One option:
>
> 1) Import into staging table as varchar field.

I had thought of that.

It would be really helpful to be able to reposition columns in tables.  That 
way, one could:
add the new TIMESTAMP column,
populate it using to_timestamp(),
drop the text column,
reposition the TIMESTAMP column to where it "should" be.

-- 
Born in Arizona, moved to Babylonia.



pgsql-general by date:

Previous
From: Ron
Date:
Subject: Re: COPY and custom datestyles. Or some other technique?
Next
From: 任重
Date:
Subject: Get dead tuples data