Here is an article about PITR in Neon
https://neon.tech/blog/point-in-time-recovery-in-postgres
12 karma · joined February 26, 2018
Today, we want to share the story of tracking down and fixing that regression, which turned out to be in the Pageserver’s walredo mechanism.
CREATE INDEX semantic_image ON image_table USING hnsw (v dist_cos_ops) WITH (M=5, ef=30, ef_construction=30, dims=512);
This is different from the dataset we used. We used GIST-960. It could interesting to test different vector store indeed.
The data is also offloaded to S3. Here is a diagram that describes the architecture: https://neon.tech/_next/image?url=https%3A%2F%2Fneon-hwp.dre...
We experimented with SELECT 1, so most of the latency is transit