The error in your deployment logs ("failed to exec pid1") is your container's init system failing to find its entrypoint inside the image, not a volume mount problem. The volume currently attached to your Postgres service is mapped to /var/lib/postgresql/data, which is the standard Postgres data path.

The other volume you referenced is currently attached to your web service in this same project. Can you confirm whether it was previously attached to Postgres and got moved? If so, we can swap them back, but Postgres will also need a redeploy to fix the entrypoint issue.

Yes, please swap the volumes back. The volume vol_upo9a91iqhj8gx25 should be attached to the web service (mounted at /app/outputs), and the PostgreSQL service should have its own correct volume. After the swap, please redeploy both services. The web service was working correctly before May 20 when this started.

We checked the current volume configuration and the volumes are already correctly attached: postgres-volume is on your Postgres service and web-volume is on your web service. No swap is needed. Your web service is also running fine. Could you confirm you are good?

The Postgres crash is caused by a stale container image, not a volume issue. Your data is intact. To fix it, open your Postgres service, press Cmd+K (or Ctrl+K) to open the command palette, and select "Redeploy source image". This re-pulls a fresh image and resolves the pid1 error. A normal redeploy from the three-dot menu won't work here since it reuses the cached image.