Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
pgbouncer reporting "FIXME: query end, but query_start == 0" on what appears to be each sql statement issued #2522
Steps to reproduce
I can reproduce at will locally, but do not know how to tell someone else to repro.
Here is an excerpt from our pgbouncer log file:
This doesn't appear to have any known adverse affect other than adding quite a bit more hay to the haystack of our pgbouncer log files, thereby making the needles harder to find.
We can easily reproduce, so if you potentially have a debug build that we could run against our dev server, perhaps we can determine exactly why pgbouncer isn't seeing our query_start.
Further technical details
@joecarr without any sort of repro it won't be possible to do much...
But if you can repro reliably on your end, it shouldn't be too hard. I suggest trying to narrow down the scenario, isolating the statement (or statements) that triggers the error, to the minimal set of actions required to trigger this. Then, you'd ideally post the database schema and sequence of actions and the pgbouncer folks should be able to take it from there.
You can easily do a debug build of Npgsql but I'm not too sure that will help you much. If you want to build, simply clone the repo, checkout the v4.0.7 tag and build.
And this will write 2 lines in pgbouncer log on each call: