-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
pq: operator does not exist: character varying =?
#1457
Comments
Please set |
What's the postgres version you're running? |
v9 |
Which version did you upgrade from? |
I did not. This is a clean dev-only install. EDIT: going to eat something now. I'll be back in a few hours. |
Have you tried the quickstart with postgres? Also make sure you have at least PG 9.6+. No tests are failing (connecting to a mysql/pg/cockroach is required for all e2e tests) so it's most likely something in your environment. |
Yes, I had that and then some working. And then I added tracing and it all crashed. |
If you disable tracing, does it work again? |
Yes. |
Ok, that will help with identifying the issue. Most likely something driver-related. |
Encountered same issue, seems like invalid placeholder is being used for postgres - '?' instead of '$1'. |
@shaxbee I don't think it's a problem with using |
Describe the bug
After installing and migrating, and then having trouble with redirects+CORS, I decided to add jaeger. This may or may not have something to do with the bug, but after reconfiguring Hydra to use the deployed Jaeger instance, I got this error:
causing Hydra to crash.
Not sure how to reproduce; it happened after a configuration change.
Server logs
Server configuration
Expected behavior
Hydra should not by its own decide not to start. In prod, this would have caused a huge outage.
Environment
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: