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 │
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.
