COPY DATABASE fails on v1.0.0 and segfaults on v1.1.0

### What happens?

I can connect to and copy tables from a PostgreSQL (running in Docker on my laptop), but if I try to copy the database I get a segmentation fault on v1.1.0, leaving behind a `.wal` file.
On v1.0.0 I get `Not implemented Error: Entry type Index not supported in PhysicalCopyDatabase`.
I don't imagine the steps I've shown to reproduce it will be much help. Let me know what I can do to help you narrow it down.

### To Reproduce

```
$ duckdb pg_local.duckdb
v1.1.0 fa5c2fe15f
Enter ".help" for usage hints.
D ATTACH 'postgresql://dev@127.0.0.1:5435/tqc' AS tqc (TYPE POSTGRES);
D COPY FROM DATABASE tqc TO pg_local;
zsh: segmentation fault duckdb pg_local.duckdb
```

```
$ duckdb-1.0 pg_local.duckdb
v1.0.0 1f98600c2c
Enter ".help" for usage hints.
D ATTACH 'postgresql://dev@127.0.0.1:5435/tqc' AS tqc (TYPE POSTGRES);
D COPY FROM DATABASE tqc TO pg_local;
Not implemented Error: Entry type Index not supported in PhysicalCopyDatabase
```

### OS:

MacOS

### PostgreSQL Version:

12.19

### DuckDB Version:

1.1.0

### DuckDB Client:

duckdb

### Full Name:

James Gilbert

### Affiliation:

Wellcome Sanger Institute

### Have you tried this on the latest `main` branch?

- [X] I agree

### Have you tried the steps to reproduce? Do they include all relevant data and configuration? Does the issue you report still appear there?

- [X] I agree