MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: 8bit
Date: Mon, 19 Jun 2017 09:54:26 +0200
From: vinny <vinny@xs4all.nl>
To: Saiful Muhajir <saifulmuhajir@gmail.com>
Cc: pgsql-sql@postgresql.org, pgsql-sql-owner@postgresql.org
Subject: Re: Find rows with "timestamp out of range"
In-Reply-To: 
 <CAA0dH_v08fBFWp+4TsRz8wESSp8zgKCL_Sdc-OVdA3vQd_XjUg@mail.gmail.com>
References: 
 <CAA0dH_v08fBFWp+4TsRz8wESSp8zgKCL_Sdc-OVdA3vQd_XjUg@mail.gmail.com>
Message-ID: <a1996168394c6d8a702b4cf9160f177e@xs4all.nl>
User-Agent: XS4ALL Webmail
Precedence: bulk
Sender: pgsql-sql-owner@postgresql.org

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.


-- 
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql