This project is archived and is in readonly mode.
Bug in 2.3.2 when connecting via pgpool?
-
Daniele Varrazzo
Hello Kevin,
I've honestly done little with pgPool/pgBouncer, so I don't know if everything we expect from the behaviour of a connection is still true when getting them from a connection pool. I've tried to run the test suite with a stock pgBouncer configuration and many tests fail: there is probably something to study in psycopg/external pool interaction, and maybe something we can expect it won't work.
I don't know, for instance, if notify works at all with pooling, as it seems ypu need to be served always from the same session, assumption I don't give as granted with a pooler in the middle.
It's hard to tell what an intermittent problem may be caused from. It may be helpful if you could compile psycopg in debug mode (see setup.cfg) and run it with the debug messages on (setting the env var PSYCOPG_DEBUG=1 when running): if the program gets stuck we may then know where.
I think we need a chat with the guys in the pooling department: Marko Kreen comes me to mind. As soon as we have the ML back again (should be soon) I'd really want to see if we are doing anything wrong and to improve the psycopg/pools interaction.
-
Daniele Varrazzo
- Tag set to notify, pgpool
-
Daniele Varrazzo
Hi Kevin,
Have you done any progress studying this problem? I've not been able to play with pgpool yet.
My understanding is that your listen command will go to a random connection so the notification will be missed by any client attached to the pool. I think the connection that has to receive the notification should be handled outside the pool.
Can you confirm that? thanks.
-
Daniele Varrazzo
- State changed from new to invalid
I assume there is not much to do and close the ticket.
I think we can have a chat about how psycopg should behave with middleware on the mailing list.