Re: segmentation faults with psycopg2 and multiprocessing

From: Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com>
To: Ryan Kelly <rpkelly22(at)gmail(dot)com>
Cc: psycopg(at)postgresql(dot)org
Subject: Re: segmentation faults with psycopg2 and multiprocessing
Date: 2012-09-28 19:20:49
Message-ID: CA+mi_8YAMDv7_dp8A4zpqF6dCZZsrVEx-7V9pxH_Tm7ge=nA_g@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: psycopg

On Fri, Sep 28, 2012 at 8:01 PM, Ryan Kelly <rpkelly22(at)gmail(dot)com> wrote:
> Hello:
>
> I am using psycopg2 and multiprocessing (and have been for quite some
> time). However, my application recently needed a connection to a new
> database. After adding this connection, I am receiving segmentation
> faults back in the parent process. I do not use the original connections
> in the child process. I create new database connections in the children.
> Does anyone have any idea about what the problem might be here?

Can you produce a traceback?

-- Daniele

In response to

Responses

Browse psycopg by date

  From Date Subject
Next Message Ryan Kelly 2012-09-28 20:24:36 Re: segmentation faults with psycopg2 and multiprocessing
Previous Message Ryan Kelly 2012-09-28 19:01:09 segmentation faults with psycopg2 and multiprocessing