Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

scrottie (4167)

scrottie
  scott@slowass.net
http://slowass.net/

My email address is scott@slowass.net. Spam me harder! *moan*

Journal of scrottie (4167)

Saturday May 05, 2007
12:20 AM

Postgres biting my bag

[ #33203 ]

message type 0x43 arrived from server while idle
message type 0x5a arrived from server while idle
22169: child_exit_handler: 20070504 22:06:20: ended with status code 0
22169: child_exit_handler: ended from signal 0
Warning: something's wrong at GDSLogger.pm line 147, line 1.
DBD::Pg::st execute failed: ERROR: prepared statement "dbdpg_6" does not exist
column number 0 is out of range 0..-1 ... that's after removing /usr/local/include/pg*.h, rebuild the latest Postgres from scartch (and then repeating all this with the last of the previous branch), rebuilding the latest DBI and DBD::Pg, undumping the database, and restarting the app that emit the daignostics above. This is after a setup that had been working fine suddenly and unexpectedly stopped working. Literally, one night, I was working on the code and everything was fine. I was working on tests, not actual code, and things were going well. The next day, it starts giving "server closed unexpectedly" diagnostics and dieing. I've been on a three day long quest to make Postgres work on this machine again. The only thing I haven't done: Reboot Linux.

-scott

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.