-
Notifications
You must be signed in to change notification settings - Fork 418
Random issue with creating pool #158
New issue
Have a question about this project? No Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “No Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? No Sign in to your account
Comments
Yes, I'm hitting the same problem, trying out PG 10beta1. Maybe unrelated, but PG emits the following immediately before the error:
|
Can you guys reproduce this with stable Postgres? |
I tried, but was unable to unfortunately. In the DB tests suite of my application, all is good with 9.6.3, while with PG10b1 it never finishes correctly, at least one out of the more of 70 tests fails, never at the same point. |
Of course I'm willing to try harder, if you have some hint on how to dig further. |
FWIW I've noticed this error lately too in a config that was working fine. I see this post is about 5 days old and the last update on the postgres dockerhub is 6 days ago. Please see the issue referring to this one for my fix.. not sure if it's relevant here. |
FYI, the same happens against the PG10b2 hub.docker.com official image. |
I spent a few more hours trying to distill a recipe to reproduce the problem, and this is the result. I hope it at least helps in determining if the problem is with the PG beta image or not. |
Thank you very much, @lelit! We'll take a look at this in detail soon. |
@lelit This seems to be an issue with the docker image. I could not reproduce on a locally built version of PostgreSQL 10 beta 2. |
Ok, thank you both! |
FYI, I posted the recipe (augmented with an alternative the uses plain docker) also on the docker-library/postgres #308. |
Uhm, the problem is still there in PG10b3. |
FYI I'm convinced this is an issue with the image and not clients. I was using nodejs at work when I reported the issue, but now using asyncpg in my own personal thing and the image is ok if password isn't set. |
Not doing so makes Cython wrap the result with __Pyx_PyObject_AsWritableString, which causes data loss if there is a NULL-byte in the middle of the returned char* buffer. While at it, constify the pointers returned by ReadBuffer methods, as the returned data is not supposed to be modified. Fixes: #158.
Yay, I confirm that my recipe works now, thank you! |
The final version of PG 10 is out, yay! 🎆 🍻 I wonder if you have an ETA for a new release of asyncpg? |
We need to deal with a couple of open PRs and will cut the release shortly thereafter. |
uvloop?: yes
Hi, I have random issue with creating pool - sometimes (about one of 5 attempts) password authentication fails =(
Here is code:
Traceback:
Postgres log:
Of course, it may be issue of Postgresql 10 beta.
Thanks.
The text was updated successfully, but these errors were encountered: