Y.

Building on #803: * extend `PostgresMemberGuard` to accept parameters * hoist as many guards as possible in the `PostgresTableReader` API * make `PostgresTableReader` ctor trivial to make sure we never...

For now only for trivial `T (func*)` ones.

Whenever a Postgres error is thrown and capture by our C++ code (or in DuckDB) we were re-throwing a generic `duckdb::EXECUTOR` for no specific reason. Instead this PR throws a...

Fix crash on `SAVEPOINT` is not supported

1

Fixes #761, #820

[chore]: Introduce lock check for some functions

1

### Description Following this comment https://github.com/duckdb/pg_duckdb/pull/415/files#r1837875339 we want to introduce a way to ensure certain non-thread safe functions are indeed called under a lock.

### 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.

Give a default value to `HTTPUtil::InitializeParameters`

2

When working on related code I realized that `optional_ptr` was not used in the `HTTPUtil::InitializeParameters` method and hence the `url` wasn't either in the related helper. This PR simply removes...

### Description As discussed in https://github.com/duckdb/pg_duckdb/discussions/832#discussioncomment-13441202

Closes https://github.com/duckdb/pg_duckdb/issues/711