Thread: Some odd postgres errors.
Greetings, everyone. I've got a Postgres system version 7.1-1 on RH 6.2 here, and I'm getting a whole host of errors. There is an import program that runs daily from a group of CSV files uploaded to a server. Since monday, it's been having problems, and I can't find anything in the import files. Here are some of the errors below. Some are obvious (invalid float, etC) but the 'bits moved right off the end of the world' is worrisome, as is Invalid XID in t_cmin.. I've got myself and three others hunting down reasons, but to no avail yet. We are debating upgrading postgres, although that worries us to, as this is a production system. Help ? Jan 26 05:04:26 web postgres[26288]: [129-2] ^IRecreate the index. Jan 26 05:04:26 web postgres[26288]: [130] ERROR: Invalid XID in t_cmin (2) Jan 27 01:45:20 web postgres[26368]: [285-1] FATAL 1: _bt_restscan: my bits moved right off the end of the world! Jan 27 10:17:48 web postgres[7450]: [55] FATAL 1: This connection has been terminated by the administrator. Jan 27 11:05:07 web postgres[11401]: [23] ERROR: Memory exhausted in AllocSetAlloc(842608949Jan 27 15:18:18 web postgres[20059]: [65] ERROR: Bad float8 input format '3536.34.0000') -- Adam Bultman adam.bultman@iconideas.com 616-836-7213 http://www.iconideas.com
Adam Bultman <adamb@iconideas.com> writes: > I've got a Postgres system version 7.1-1 on RH 6.2 here, and I'm getting > a whole host of errors. > There is an import program that runs daily from a group of CSV files > uploaded to a server. Since monday, it's been having problems, and I > can't find anything in the import files. Here are some of the errors > below. Some are obvious (invalid float, etC) but the 'bits moved right > off the end of the world' is worrisome, as is Invalid XID in t_cmin.. I would recommend running some memory and disk diagnostics. That invalid XID error doesn't suggest anything but corrupted data to me. Some of the other errors you quote look downright bizarre as well. Hardware problems seem like a very plausible explanation for all. > I've got myself and three others hunting down reasons, but to no avail > yet. We are debating upgrading postgres, although that worries us to, as > this is a production system. You should definitely update to 7.1.3, or whatever the last of the 7.1 series was. We do not make dot-releases for entertainment value --- if there's a dot-release later than what you have, it was put out to fix significant bugs. Updating to 7.2 or 7.3 series would be even better, but is significantly more likely to create application compatibility issues (not to mention that you'd need a dump and restore), so it's not quite such a no-brainer decision. regards, tom lane
> > I've got myself and three others hunting down reasons, but to no avail > > yet. We are debating upgrading postgres, although that worries us to, as > > this is a production system. > For what its worth, I just upgraded (just = today) from 7.1.2 to 7.3.1 and it was a BREEZE. I have > 6M records on my production box. I ran both systems at the same time and pgdumpall'd to the new DB. It was SO slick! Oh and just for the record. I LOVE POSTGRESQL!!! :) As tom said however if you have application issues it might be tougher. My 2 bits Chad