-
Notifications
You must be signed in to change notification settings - Fork 916
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “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? Sign in to your account
implement ConnPrepareContext/StmtQueryContext/StmtExecContext interfaces #1047
Conversation
9f33411
to
8cb9b67
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My gut with this is the same as #921 (comment) -- there are too many goroutines and channels for me to feel comfortable. But given that we already do this for the conn
implementation, maybe we're ok.
Some testing changes needed.
55727bb
to
b5ce7c4
Compare
well looks like CI no longer works :\ |
Yea looks like they deprecated travis-ci.org in favor of travis-ci-com. not sure what needs to happen to move this project over. Let me know if I can help. |
Looks like all you have to do is sign up on the .com? |
i've tried that and resent the webhooks but no bueno, perhaps try i don't have admin permissions to debug this further unfortunately (travis-ci.com doesn't show this repo when i try configure it there), may have to move to a new CI system. /shrug |
94c98c3
to
200830e
Compare
I was able to add my fork here: https://travis-ci.com/github/michaelshobbs/pq/builds/235721359 I assume that's because I own it. Who is still an admin on this repo? 😬 |
@otan where did we end up and is there anything i can do to help? |
You'd need to find who the admin is :) Idk who it is. Maybe @mjibson knows. |
I do not! |
Well I think the answer to get CI working (and for me to have confidence in merging) we'd need to migrate to Github Actions. I don't have the time to do this, such is maintenance life :\ |
FYI I previously tried really hard to make github actions work at 8cec546. I was never able to get the pg initial configuration files correctly installed before the pg server started running. But that commit is like almost all there. |
It looks like the scripts should be mounted at |
gotcha |
Sweet! I'll start working on this in the morning |
Hi! |
Quick update @michaelshobbs. We have tested your patch (just replaced the go.mod to your fork) and it seems still not to work on prepared statements. Our usecase: add 10sec timeout to context from and send a db query on a prepared statement which last longer, than 1 minute. |
@DoubleDi can you provide some code that demonstrates the incorrect behavior? this PR includes |
@michaelshobbs I am not exactly sure, but in some cases, this works. I can see the |
200830e
to
151165d
Compare
151165d
to
0e61f02
Compare
0e61f02
to
9fa33e2
Compare
@otan thanks! Please also tag a new release |
v1.10.3, you have to be a tad more patient than 90s :P |
thank you so much! |
See #1046 for more context. (pun intended)
This is almost a line for line copy of #921 with test cases (thanks @kylejbrock). Please let me know what else needs to be done to get this merged.
Also dropped ci testing of unsupported versions (9.5 and 9.4) per pg docs here and added ci testing of versions 11, 12, and 13.
closes #921
closes #1046