From: T E Schmitz <mailreg@numerixtechnology.de>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-sql@postgresql.org
Subject: Re: pg_dump fails (timestamp out of range)
Date: Mon, 26 Feb 2007 11:05:08 +0000
Message-ID: <45E2BEE4.5090003@numerixtechnology.de> (raw)
In-Reply-To: <5458.1172159013@sss.pgh.pa.us>
References: <45DD82AC.2030800@numerixtechnology.de>
<5458.1172159013@sss.pgh.pa.us>
Tom Lane wrote:
> T E Schmitz <mailreg@numerixtechnology.de> writes:
>
>>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.
Dear Tom,
I can't thank you enough for the above advice. The test above identified
3 records and once they were removed I was able to dump the DB.
--
Best Regards,
Tarlika Elisabeth Schmitz
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: mailreg@numerixtechnology.de, tgl@sss.pgh.pa.us
Subject: Re: pg_dump fails (timestamp out of range)
In-Reply-To: <45E2BEE4.5090003@numerixtechnology.de>
* 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