Hi, I'm experiencing a very troublesome problem with my application, after a lot of digging and searching I haven't been able to solve it. The problem is this: I have a python program executing (blocking, waiting for it to return) a second python program where both use pygresql. The second python program unfortunately has a tendency to hang completely on a "random" (always a write query) query. When the main application hangs because it is waiting for the "inner" app to quit I can press ctrl-c. This yields the following error printed by the try/catch around the SQL statement:
internal error in 'UPDATE muxes SET network_name = 'Hotbird 6' WHERE original_network_id = '318' AND transport_stream_id = '13100'': Postgres's log prints: FATAL: 08P01: invalid frontend message type 32 LOCATION: SocketBackend, postgres.c:380 postgres.c:380 is an error triggered when there is a communication error which leads me to think that this might be a pygresql problem (although I might be very very wrong here) The strange thing is that I've not been able to reproduce the problem if I run only the "inner" of the two applications. Tried both with postgresql 8.0.8 and 8.1.4, pygresql 3.6.2 and 3.8. Any guru who lerks around on this list who is able to shed some light on this issue? I would be extremely thankful for any hint that can help me solve it. Cheers, Frederik -- Time was invented by carbon based lifeforms in order to monitor their ongoing decay _______________________________________________ PyGreSQL mailing list [email protected] http://mailman.vex.net/mailman/listinfo/pygresql
