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:

--
================================================== ================
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 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

Achilleus Mantzios <achill (AT) matrix (DOT) gatewaynet.com> writes:
Is it possible you have any really wacko timestamp values in your data?
This looks like this recent report:
http://fts.postgresql.org/db/msg.html?mid=1505105
but I dunno if it's the same problem.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org