Erik JohnstonandClaude Opus 4.8 f7e12aef2d Add GIL-releasing block_on helpers on the shared tokio runtime ...

Add the `block_on`/`block_on_result`/`block_on_next` helpers the Postgres
backend uses to drive its async `tokio-postgres` futures to completion from
sync, GIL-holding Python methods, releasing the GIL for the wait. They take
a `tokio::runtime::Handle` and block on it from the calling (Python) thread.

Rather than give the DB backend a runtime of its own, they use the
extension's existing shared runtime (`tokio_runtime::PyTokioRuntime`, stored
on the reactor). `start` is made idempotent and a `runtime_handle` accessor
starts it on demand, so a caller that needs a connection before the reactor
is running still gets a handle; once the reactor runs, its
`callWhenRunning(start)` hook is a no-op.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01RPEeXx2fAG67o6u4CnmC8W

2026-07-23 14:35:04 +00:00

..

benches

Implement the push rules for experimental MSC4306: Thread Subscriptions. (#18762)

2025-08-06 15:33:52 +01:00

src

Add GIL-releasing block_on helpers on the shared tokio runtime

2026-07-23 14:35:04 +00:00

build.rs

resolves #19403 Report the rust compiler version used in the prometheus metrics (#19643)

2026-04-03 11:21:23 +02:00

Cargo.toml

Add Postgres value mapping for the Rust database backend

2026-07-23 14:35:03 +00:00