> would help to grab a query ID. A second option I have in mind would
> be to set up an injection point that produces a NOTICE if a query ID
> is set when we end processing an execute message, then check the
> number of NOTICE messages produced as these can be predictible
> depending on the number of rows and the fetch size.. This won't fly
> far unless we can control the fetch size.
FWIW, I do like the INJECTION_POINT idea and actually mentioned something
similar up the thread [1] for the revalidate cache case, but I can see it being applied
to all the other places we expect the queryId to be set.
[1] https://www.postgresql.org/message-id/465EECA3-D98C-4E46-BBDB-4D057617DD89%40gmail.com
--
Sami
