`IsExtensionRegistered` should not be called in an aborted transaction
Open
- Dominant language
- C++
- Stars
- 3.2k
- Forks
- 204
- PR merge metrics
- No merged PRs in 30d
Description
### Description
Follow-up of Issue https://github.com/duckdb/pg_duckdb/issues/336
We made a small patch to prevent the crash, but we shouldn't call `IsExtensionRegistered` in the an aborted transaction in the first place.
Contributor guide
Research direction
Start by reading Issue 336 and the existing crash-prevention patch, then trace where IsExtensionRegistered is reached during transaction handling. Done means the check is not reached for an aborted transaction and the reported crash remains prevented; the payload names no files or tests to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, postgresql
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100