add `queryId` to `CompiledQuery` to allow async communication between more components.

[igalklebanov]

does what #173 tried to achieve, but in a simpler way as suggested by @koskimas.

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
kysely	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 7, 2024 8:12pm

[alexgleason]

Thank you for continuing to update this branch @igalklebanov

What do you think of this PR @koskimas? Are you going to merge it? This issue has been open for 2 years. I understand not wanting to break things, because it will be a pain to deal with. I am an open source maintainer, I get it. But serious projects really need this. It is essentially broken already to me, in its current state. Because my services are doing this constantly and I don't really have a good way to deal with it in Kysely. I feel backed into a corner.

I have spent the past two weeks gathering data to try to fix this. I came up with this graph (query duation):

And it is very symetrical with this graph (available connections):

That causes downtime. I need to cancel queries after a timeout.

I am planning to try some postgres workarounds, like using set statement_timeout in a transaction. But that is a hack. I would really like a real solution. Thank you.