From: Tom Lane <tgl@sss.pgh.pa.us>
To: mailreg@numerixtechnology.de
Cc: pgsql-sql@postgresql.org
Subject: Re: pg_dump fails (timestamp out of range)
Date: Thu, 22 Feb 2007 10:43:33 -0500
Message-ID: <5458.1172159013@sss.pgh.pa.us> (raw)
In-Reply-To: <45DD82AC.2030800@numerixtechnology.de>
References: <45DD82AC.2030800@numerixtechnology.de>
T E Schmitz <mailreg@numerixtechnology.de> writes:
> However, I am stalled because pg_dump fails with the following error:
> pg_dump: ERROR: timestamp out of range
> pg_dump: SQL command to dump the contents of table "server_hit_bin"
> failed: PQendcopy() failed.
You should treat this as a corrupt-data exercise: you need to identify
and fix (or delete) the offending row(s). In this case you might try
tests like "bin_end_date_time > '1 Jan 9999'" and so on to see if you
can determine exactly which rows are bad.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, mailreg@numerixtechnology.de
Subject: Re: pg_dump fails (timestamp out of range)
In-Reply-To: <5458.1172159013@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox