After a pg_lakehouse
error, subsequent queries crash with "there is no reactor running"
#1136
Labels
bug
Something isn't working
pg_lakehouse
Issue related to `pg_lakehouse/`
priority-1-high
High priority issue
Bug Description
After a runtime error in a
pg_lakehouse
query, we're stuck with:How To Reproduce
Follow quickstart to
CREATE FOREIGN TABLE trips
.Turn off wifi, so that the extension cannot talk to AWS.
Run
SELECT COUNT(*) FROM trips;
, which should produce:Run
SELECT COUNT(*) FROM trips;
again, which produces:The error persists until the extension is reloaded.
The text was updated successfully, but these errors were encountered: