Finally i found the bad row in the bad table.
My wondering is that
a) java.sql.Timestamp.valueOf(String) accepts
yyyy-MM-dd hh:mm:ss.fff
b) when i try
UPDATE noonmsg SET eta = '4714-01-01 BC';
i get
ERROR: TIMESTAMP WITH TIME ZONE out of range '4714-01-01 BC'
c) the girl who does data entry has no clue of what keys she pressed
I am curious if this will happen to anyone again.
On Wed, 2 Jul 2003, Achilleus Mantzios wrote:
>
> Also,
> % pg_dump -t noonmsg dynacom > noonmsg_dump.sql
> pg_dump: ERROR: Unable to format timestamp with time zone; internal
> coding error
> pg_dump: lost synchronization with server, resetting connection
> pg_dump: SQL command to dump the contents of table "noonmsg" failed:
> PQendcopy() failed.
>
> Also,
>
> # ANALYZE/pg_dump seems to work with other tables.
>
> Are there any thoughts on that?
>
> On Wed, 2 Jul 2003, Achilleus Mantzios wrote:
>
> >
> > dynacom=# SELECT version();
> > version
> > -------------------------------------------------------------
> > PostgreSQL 7.3.3 on i686-pc-linux-gnu, compiled by GCC 2.96
> > (1 row)
> >
> > dynacom=# VACUUM ANALYZE ;
> > ERROR: Unable to format timestamp with time zone; internal coding error
> > dynacom=# VACUUM ;
> > VACUUM
> > dynacom=# ANALYZE ;
> > ERROR: Unable to format timestamp with time zone; internal coding error
> >
> >
> > Anyone knows whats going on??
> >
>
>
--
==================================================================
Achilleus Mantzios
S/W Engineer
IT dept
Dynacom Tankers Mngmt
Nikis 4, Glyfada
Athens 16610
Greece
tel: +30-210-8981112
fax: +30-210-8981877
email: achill at matrix dot gatewaynet dot com
mantzios at softlab dot ece dot ntua dot gr
---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings
