| From: | Graham Leggett <minfrin(at)sharp(dot)fm> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Unable to format timestamp with time zone; internal |
| Date: | 2002-12-22 13:39:26 |
| Message-ID: | 3E05C08E.9010207@sharp.fm |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Tom Lane wrote:
>> pg_dump: ERROR: Unable to format timestamp with time zone; internal
>>coding error
>
>
> AFAICT this error can only appear when trying to display a timestamp
> that's before the start of the Julian day count, 4713 BC ... which the
> system should never have let you enter in the first place. (In my
> tests, the timestamp input routine rejects such dates.) Got any idea
> how you got that value in there?
Absolutely no idea. Could vacuuming the database affect it?
Any idea what solution I can use to fix this? We can no longer back up
our database any more, which is a critical problem.
Why is this a fatal error? Is there a way of turning this into a warning
so we can at least get the rest of the data out?
Regards,
Graham
--
-----------------------------------------
minfrin(at)sharp(dot)fm "There's a moon
over Bourbon Street
tonight..."
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Graham Leggett | 2002-12-22 14:26:57 | Re: Unable to format timestamp with time zone; internal |
| Previous Message | Stephan Szabo | 2002-12-22 04:31:31 | Re: drop foreign key |