Eric Ridge

Ahh. Yes. Thanks!

I realize this issue is nearly a year old now, but is the complaint here simply that we accidentally spelled `boundary_max_scan` (what ES actually wants) as `boundary_scan_max`? If so, I'll...

> it's just a mess to manage builds for. which is why we would have loved to see someone from the Nix community actively send us PRs and keep it...

I’m sorry. Did we close a PR from you and I’m missing something? Looking through the history here and in the other issues, looks like things were last discussed here...

> I don't know how you could ever expect someone that gives a crap to actually contribute under these circumstances sounds like a combination of a communications problem and an...

Sweet. We’ll look forward to the PR and work with you to help us make sure it’s something easy for everyone to maintain as time goes on.

> I asked @NotGyro to take a look at this. Unfortunately, it seems to be a bit tougher than expected. Implementing the patch in cargo-pgrx is easy, and that was...

That code isn't included in plrust user functions. Only in plrust proper

> @eeeebbbbrrrr I just stumbled across this: https://pgt.dev/ Wonder if it could be a universal solution to the deployment problem? Probably. I'm friendly with those folks and I expect they'll...

I haven't checked out this branch to play with it, but can a cursor escape an Spi::connect() block? Like, does this compile: ```rust let cursor = Spi::connect(|mut client| { let...