From: | Saiful Muhajir <saifulmuhajir(at)gmail(dot)com> |
---|---|
To: | vinny <vinny(at)xs4all(dot)nl> |
Cc: | pgsql-sql(at)postgresql(dot)org, pgsql-sql-owner(at)postgresql(dot)org |
Subject: | Re: Find rows with "timestamp out of range" |
Date: | 2017-06-19 07:57:58 |
Message-ID: | CAA0dH_timQKR659Op4MG52oCOVrOdG9rfFh+-FUD6R-AwM4ahA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Yes, I am sure.
Table "public.comments"
Column │ Type │
Modifiers
─────────────────┼─────────────────────────────┼──────────────────────────────────────────────────────────────
comment_id │ bigint │ not null default
nextval('comments_comment_id_seq'::regclass)
user_id │ bigint │ not null
status │ smallint │ not null default 1
message │ text │ not null
create_time │ timestamp without time zone │ not null default now()
update_time │ timestamp without time zone │
--
Regards,
Saiful Muhajir <http://saifulmuhajir.web.id>
On 19 June 2017 at 14:54, vinny <vinny(at)xs4all(dot)nl> wrote:
> On 2017-06-19 09:11, Saiful Muhajir wrote:
>
>> Hi,
>>
>> I have a table with around 133 MILLION ROWS with two timestamp
>> columns. While trying to copy some columns for a new database, using
>> \COPY , the error occurred with: TIMESTAMP OUT OF RANGE
>> While trying to figure out the rows containing the out of range
>> value, I am using this with no result:
>>
>>
> Are you sure that CREATED_AT is a timestamp? It seems odd that
> the database would contain an invalid timestamp value in a timestamp field.
>
From | Date | Subject | |
---|---|---|---|
Next Message | Samed YILDIRIM | 2017-06-19 08:37:34 | Re: Find rows with "timestamp out of range" |
Previous Message | vinny | 2017-06-19 07:54:26 | Re: Find rows with "timestamp out of range" |