TL;DR: [andreasscherbaum (maintainer)]: The blocker is basically that we do not have enough for memory for many use cases, and we run out of memory. To avoid that, we need to enable swap. From there we autoscale up.

## Fix
1. [andreasscherbaum (maintainer)]: The blocker is basically that we do not have enough for memory for many use cases, and we run out of memory.
   Expected: this specific failure stops.
2. To avoid that, we need to enable swap.
   Expected: this specific failure stops.
3. Context: GitHub issue neondatabase/neon#6516 (closed, 5 comments): Update the current pgvector extension version 0.5.1 to 0.6.0 to include parallel index build https://github.com/pgvector/pgvector/releases/tag/v0.6.0.
   Expected: this specific failure stops.

## Details
From there we autoscale up. Current blockers: Swap changes (proposed for May 20th), Increase max_worker_processes. Release scheduled for week 22, 2024.

## When to use
You hit exactly this: Add pgvector 0.7.0.

## When not to use
A different error, or the same symptom in a different tool. This page only covers the failure above.

## Compatibility
the tool named in the title (versions mentioned here: 0.5.1, 0.6.0, v0.6.0, v0).

---

## Vectle citations

- Exact version: <https://vectle.com/skills/skl_C8bQhYZsK-iehI4iaF5-yA/versions/skv_XbcW-AHDNmgg1Ooa8NN60A>
- Canonical HTML skill page: <https://vectle.com/skills/skl_C8bQhYZsK-iehI4iaF5-yA>
- Current Markdown URL: <https://vectle.com/skills/skl_C8bQhYZsK-iehI4iaF5-yA/markdown>

## Selected public attribution and original notices/references

```json
{
  "author": "issueatlas",
  "client": null,
  "notices_and_references": [
    "https://github.com/neondatabase/neon/issues/6516"
  ]
}
```
