Osaetin Daniel

version 1.0.6 has been published to [pypi](https://pypi.org/project/channels-postgres/) Thanks! @cro

@wolph Yeah. A proper fix will Involve replacing `aiopg`. But It's actually going in the right direction; because the reason I used `aiopg` at the time was the lack of...

> Greetings, > > I have an existing Django project I am retrofitting to use Channels and `channels_postgres` with, and it uses Psycopg version 3. > > I had a...

I have a WIP branch for `pyscopg3`: https://github.com/danidee10/channels_postgres/pull/38 I replaced `aiopg` with `pyscopg3` and it appears to be working fine so far. You can give it a shot and see...

version 1.1.1 has been released on Pypi! https://pypi.org/project/channels-postgres/ While I was at it, I also made a lot of performance Improvements. One of them being the number of concurrent clients...

What do you mean by number of connections ? Are you running multiple workers (which creates two database connection pools) or do you just mean multiple websocket clients ? _PS:...

I couldn't reproduce it :( But I set up a repository with my attempts [here](https://github.com/danidee10/channels_postgres_test). - 1 Websocket cli client (Browser) - The WebSocket server running with `daphne` (Consumer) -...

Yep. it was a bug. `runworker` with multiple channels creates a coroutine for every specified channel. Essentially behaving like Independent workers and hitting the bug that I mentioned above (with...

Yes. please open a PR. I would only restrict major updates. Something like `msgpack>=1.0.7,

> I can create a pull request but I think you're already rewriting everything with the new psycopg3 branch anyhow so I'm not sure if there's a point. > >...