Tristan Partin ebc55e6ae8 Fix logic for checking if a compute can install a remote extension (#10656) ...

Given a remote extensions manifest of the following:

```json
  {
    "public_extensions": [],
    "custom_extensions": null,
    "library_index": {
      "pg_search": "pg_search"
    },
    "extension_data": {
      "pg_search": {
        "control_data": {
          "pg_search.control": "comment = 'pg_search: Full text search for PostgreSQL using BM25'\ndefault_version = '0.14.1'\nmodule_pathname = '$libdir/pg_search'\nrelocatable = false\nsuperuser = true\nschema = paradedb\ntrusted = true\n"
        },
        "archive_path": "13117844657/v14/extensions/pg_search.tar.zst"
      }
    }
  }
```

We were allowing a compute to install a remote extension that wasn't
listed in either public_extensions or custom_extensions.

Signed-off-by: Tristan Partin <tristan@neon.tech>

2025-02-05 14:58:33 +00:00

..

src

Fix logic for checking if a compute can install a remote extension (#10656)

2025-02-05 14:58:33 +00:00

tests

Manage pgbouncer configuration from compute_ctl:

2023-12-26 15:17:09 +00:00

Cargo.toml

Remove unnecessary dependencies (#9000)

2024-09-17 17:55:45 +03:00