Fetching timeline seems very slow and always get 503 after 3.18.1 update

Support
1

I updated my instance to latest release (2026.03.1) yesterday. But when I tried to pull any timeline, the api often returns 503 and caused the exception:

Request: GET /api/v1/timelines/home?with_muted=true&reply_visibility=following&limit=20
** (exit) an exception was raised:
    ** (DBConnection.ConnectionError) tcp recv (idle): closed (the connection was closed by the pool, possibly due to a timeout or because the pool has been terminated)
        (ecto_sql 3.13.2) lib/ecto/adapters/sql.ex:1098: Ecto.Adapters.SQL.raise_sql_call_error/1
        (ecto_sql 3.13.2) lib/ecto/adapters/sql.ex:996: Ecto.Adapters.SQL.execute/6
        (ecto 3.13.4) lib/ecto/repo/queryable.ex:241: Ecto.Repo.Queryable.execute/4
        (ecto 3.13.4) lib/ecto/repo/queryable.ex:19: Ecto.Repo.Queryable.all/3
        (pleroma 3.18.1) lib/pleroma/pagination.ex:40: Pleroma.Pagination.fetch_paginated/4
        (pleroma 3.18.1) lib/pleroma/web/activity_pub/activity_pub.ex:552: Pleroma.Web.ActivityPub.ActivityPub.fetch_activities/3
        (pleroma 3.18.1) lib/pleroma/web/mastodon_api/controllers/timeline_controller.ex:71: Pleroma.Web.MastodonAPI.TimelineController.home/2
        (pleroma 3.18.1) lib/pleroma/web/mastodon_api/controllers/timeline_controller.ex:5: Pleroma.Web.MastodonAPI.TimelineController.action/2

I use a from source installation with podman. How do I solve it?

2

we’ve got a few reports of this - whilst we’re not sure as to the exact cause, running a VACUUM over the database seems to work in all cases we’ve seen so far

1 Like
3

yeah I do a full vacuum for the database, the issue seems fixed by now. thanks :slight_smile: