Would it be a good idea to shutdown postgresql and then make a backup copy
of the entire /data/ directory. Then restart postgresql and try to see how
many rows have allegedly erroneous timezone? e.g. do a select count(*)
where date < some really old date here, to see how many rows affected. Then
do a select, and then update those bad dates if only a few rows affected.
If that works then you might be able to dump your database and upgrade. Not
sure if it would be helpful to dump stuff table by table using pg_dump -
might be useful to check which table has dump problems.
Good luck,
Link.
At 04:26 PM 12/22/02 +0200, Graham Leggett wrote:
>Tom Lane wrote:
>
>>> pg_dump: ERROR: Unable to format timestamp with time zone; internal
>>> coding error
>
>I notice that v7.2.3 was released, but noone made RPMs for it, and the
>spec file in the release is hosed:
>
>[root@trilobite ~]# rpm -tb postgresql-7.2.3.tar.gz
>error: File /root/PyGreSQL-3.0-pre20000310.tgz: No such file or directory
>
>Are there any RPMs available anywhere for 7.2.3 that might fix this problem?
>
>Regards,
>Graham
>--
>-----------------------------------------
>minfrin@sharp.fm "There's a moon
> over Bourbon Street
> tonight..."
>
>
>---------------------------(end of broadcast)---------------------------
>TIP 5: Have you checked our extensive FAQ?
>
>http://www.postgresql.org/users-lounge/docs/faq.html
>