Anastasia Lubennikova 92bc2bb132 Refactor remote extensions feature to request extensions from proxy (#5836) ...

instead of direct S3 request.

Pros:
- simplify code a lot (no need to provide AWS credentials and paths);
- reduce latency of downloading extension data as proxy resides near
computes; -reduce AWS costs as proxy has cache and 1000 computes asking
the same extension will not generate 1000 downloads from S3.
- we can use only one S3 bucket to store extensions (and rid of regional
buckets which were introduced to reduce latency);

Changes:
- deprecate remote-ext-config compute_ctl parameter, use
http://pg-ext-s3-gateway if any old format remote-ext-cofig is provided;
- refactor tests to use mock http server;

2023-11-27 12:10:23 +00:00

..

src

Refactor remote extensions feature to request extensions from proxy (#5836)

2023-11-27 12:10:23 +00:00

.gitignore

Revert "Use actual temporary dir for pageserver unit tests"

2023-01-19 20:16:56 +01:00

Cargo.toml

fix: replace all std::PathBufs with camino::Utf8PathBuf (#5352)

2023-10-04 17:52:23 +03:00

safekeepers.conf

Separate mgmt and libpq authentication configs in pageserver. (#3773)

2023-03-15 13:52:29 +02:00

simple.conf

tests: enable multiple pageservers in neon_local and neon_fixture (#5231)

2023-09-08 16:19:57 +01:00