adding libpq to pgbouncer breaks single handler

From: Merlin Moncure <mmoncure(at)gmail(dot)com>
To: PostgreSQL General <pgsql-general(at)postgresql(dot)org>, pgbouncer-general(at)pgfoundry(dot)org
Subject: adding libpq to pgbouncer breaks single handler
Date: 2010-02-06 18:00:00
Message-ID: b42b73151002061000m55808f00y21c67f0da82660e0@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Having a weird issue that I just can't figure out. We are playing
with implementing listen/notify in pgbouncer. Our strategy involved
some libpq calls etc so we added libpq to the make. Doing this
completely broke pgbouncer signals...something else is catching
SIGINT. If we comment our function that makes libpq calls (with the
linker thereby optimizing out the libpq stuff), the problem goes away.
Note none of our code actually, runs, we manually raise a kill
immediately after setting up signals in pgbouncer and it doesn't get
properly caught if we have libpq linked in.

merlin

Browse pgsql-general by date

  From Date Subject
Next Message Michael Kohout 2010-02-06 19:19:52 Snow Leopard-how to get PG 8.4 to start up on demand?
Previous Message Cédric Villemain 2010-02-06 16:29:52 Re: Multiple buffer cache?