Thread: [SQL] Find rows with "timestamp out of range"

[SQL] Find rows with "timestamp out of range"

From

Saiful Muhajir

Date:

19 June 2017, 10:11:18

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:

select comment_id, create_time from comments where create_time > '1 Jan 9999';
comment_id │ talk_id │ create_time
────────────┼─────────┼─────────────
(0 rows)

The error occurred when I query with:

select comment_id, create_time from comments where create_time < '1 Jan 1800';
ERROR: 22008: timestamp out of range
LOCATION: timestamp_out, timestamp.c:226

So, how do I figure out the rows with problems?

Thank you.

Regards,

Saiful

Re: [SQL] Find rows with "timestamp out of range"

From

vinny

Date:

19 June 2017, 10:54:26

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.

Re: [SQL] Find rows with "timestamp out of range"

From

Saiful Muhajir

Date:

19 June 2017, 10:57:58

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

On 19 June 2017 at 14:54, vinny <vinny@xs4all.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.

Re: [SQL] Find rows with "timestamp out of range"

From

Samed YILDIRIM

Date:

19 June 2017, 11:37:34

Hi Saiful,

Which version of PostgreSQL do you use?

Have you ever upgrade your Postgres from earlier major releases?

What was your upgrade method (dump/restore, pg_upgrade)?

Best regards.

İyi çalışmalar.

Samed YILDIRIM

19.06.2017, 10:59, "Saiful Muhajir" <saifulmuhajir@gmail.com>:

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

On 19 June 2017 at 14:54, vinny <vinny@xs4all.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.

Re: [SQL] Find rows with "timestamp out of range"

From

Adrian Klaver

Date:

19 June 2017, 16:25:55

On 06/19/2017 12:11 AM, 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:
> 
> 
> *select comment_id, create_time from comments where create_time > '1 Jan 
> 9999';
> * comment_id │ talk_id │ create_time
> ────────────┼─────────┼─────────────
> (0 rows)
> 
> The error occurred when I query with:
> 
> 
> *select comment_id, create_time from comments where create_time < '1 Jan 
> 1800';*
> ERROR:  22008: timestamp out of range
> LOCATION:  timestamp_out, timestamp.c:226

Do you really have timestamps in create_time that are before '1 Jan 1800'?

To put it another way, what is the range of values you would expect for 
create_time?

> 
> 
> So, how do I figure out the rows with problems?

When you did the \copy and got the error, did it give you a row number 
for the error?

Have you ever had the database or computer crash?

> 
> 
> Thank you.
> 
> --
> Regards,
> 
> Saiful


-- 
Adrian Klaver
adrian.klaver@aklaver.com

Re: [SQL] Find rows with "timestamp out of range"

From

Tom Lane

Date:

19 June 2017, 16:33:10

Saiful Muhajir <saifulmuhajir@gmail.com> writes:
> 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*

> *select comment_id, create_time from comments where create_time < '1 Jan
> 1800';*
> ERROR:  22008: timestamp out of range
> LOCATION:  timestamp_out, timestamp.c:226

As you can see, the error is occurring in timestamp_out(), ie in the
attempt to display the specific value.  You could probably do this
successfully:

select comment_id from comments where create_time < '1 Jan 1800';

and to fix, maybe

update comments set create_time = '-infinity' where create_time < '1 Jan 1800';

As to what's actually going on, we made an effort a few years back to
tighten up the logic concerning exactly what is the minimum legal
timestamp value --- it's somewhere in 4714BC, but as I recall, the exact
boundary where it failed used to depend on your TimeZone setting.  (Maybe
it still does, for you ... what PG version is this exactly?)  I'm betting
that you have a value right on the hairy edge of failure, that was
accepted when input but is now rejected during display, either because of
the aforesaid logic changes or because you're using a different TimeZone
setting than it was input under.

It might be entertaining to try

select comment_id, create_time + interval '1 year'
from comments where create_time < '1 Jan 1800';

and see if that is able to produce output.
        regards, tom lane

Re: [SQL] Find rows with "timestamp out of range"

From

Saiful Muhajir

Date:

20 June 2017, 04:48:17

Hi,

I tried with

SELECT comment_id FROM comments WHERE create_time < '1 Jan 1800';

But the result is same: ERROR 22008 timestamp out of range.

With the help from #postgresql community, I successfully extract the min(create_time) with below query:

SELECT min(trim(leading '\' from timestamp_send(create_time)::text)::bit(64)::bigint) FROM comments;

min

-------

-332024613738615000

Which is in microseconds from 2000-01-01 00:00:00 and the result is correspond to ~10500 BC. Way out of range. CMIIW

So, while trying to figure out the "broken" rows with this query:

SELECT comment_id FROM comments WHERE trim(leading '\' from timestamp_send(create_time)::text)::bit(64)::bigint > -31556908800000000

And there are many rows, 800+. So, I guess this looks like corrupted data in the table.

A while ago, the server was crashed when our datacenter experienced power outage. But I didn't checked anything until today. It seems that what's left is how do I fix this because we don't store old backups.

For your information, I forgot to mention that this is Postgres 9.3.15 with fsync=ON.

Regards,

Saiful Muhajir

On 19 June 2017 at 20:33, Tom Lane <tgl@sss.pgh.pa.us> wrote:

Saiful Muhajir <saifulmuhajir@gmail.com> writes:
> 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*

> *select comment_id, create_time from comments where create_time < '1 Jan
> 1800';*
> ERROR: 22008: timestamp out of range
> LOCATION: timestamp_out, timestamp.c:226

As you can see, the error is occurring in timestamp_out(), ie in the
attempt to display the specific value. You could probably do this
successfully:

select comment_id from comments where create_time < '1 Jan 1800';

and to fix, maybe

update comments set create_time = '-infinity' where create_time < '1 Jan 1800';

As to what's actually going on, we made an effort a few years back to
tighten up the logic concerning exactly what is the minimum legal
timestamp value --- it's somewhere in 4714BC, but as I recall, the exact
boundary where it failed used to depend on your TimeZone setting. (Maybe
it still does, for you ... what PG version is this exactly?) I'm betting
that you have a value right on the hairy edge of failure, that was
accepted when input but is now rejected during display, either because of
the aforesaid logic changes or because you're using a different TimeZone
setting than it was input under.

It might be entertaining to try

select comment_id, create_time + interval '1 year'
from comments where create_time < '1 Jan 1800';

and see if that is able to produce output.

regards, tom lane