Closed gmr closed 2 years ago
After manually updating the pgq extension from v3.2.6 (which is installed via deb package from pgdg) to v3.3.1, I am seeing the same behavior.
Only potential path for it I see is weird db name. Added quoting for dbname in v3.5, that should fix it.
I'm running a custom built pgqd and running into a weird error I could not track down in the code, as there is no message:
Full output with
-v
Dockerfile:
I did notice that pgqd is 3.3 and pgq is 3.2.6, will go hunt that down and see if it's related.
Any thoughts as to what this could be?