On 7/11/07, Peter Nixon <[EMAIL PROTECTED]> wrote: ... > In any case, I listed the important packages in use on the system: > postgresql-server-8.2.4-5 > python-2.5.1-12 > python-psycopg2-2.0.6-2.5 > python-django-snapshot-5646-1 > > While these are all new packages, the only one which is "unstable" is django, > with all the others being point upgrades of existing stable releases.
Hi Peter, I'm sorry we're not more cooperative, but I think your respondents are limited because reproducing the problem requires SUSE. At any rate, I am curious if you can isolate the issue further. Obviously, the svn trunk does work for people in general. This failure sounds a bit log segfaulting from a single process loading incompatible versions of a library. Someone else in this thread reported that the problem doesn't occur when using psycopg, but does with psycopg2. Can you check ldd for psycopg2? Does the crash occur when the cursor is created, or executed, or...? Can you run the same code outside of Django (but using psycopg2 and the same data structures going into the cursor)? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
