Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Postgres: no retention or partition management for events/attempts, causing unbounded growth

Abierto
  • ¿Algo no está bien?
#1,027 4 comentarios 1 reacción 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
go, postgresql, sql
Área
databases

Línea de trabajo

Start by reading the Postgres partition definitions and migrations, including 000005_denormalize_attempts.up.sql, then review internal/logstore/pglogstore/README.md and docs/content/self-hosting/guides/event-delivery-log.mdoc. The issue asks for partition lifecycle management, a retention setting, a migration path for DEFAULT partitions, and documentation; agree on the design and supported migration behavior before implementation.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Summary

Outpost's Postgres events and attempts tables are declared as range-partitioned on time, but only DEFAULT partitions are created.

We could not find any code that creates, rotates, or drops time-based Postgres partitions, nor any built-in Postgres retention mechanism. This leaves operators implementing retention externally with row-by-row DELETE, with the associated dead-tuple, vacuum, and index-maintenance overhead.

This appears to be an incomplete part of the intended Postgres design rather than a new feature request.

Evidence in the source

The Postgres schema already uses time-based partitioning:

PRIMARY KEY (time, id)
) PARTITION BY RANGE (time);

CREATE TABLE events_default PARTITION OF events DEFAULT;

The same pattern is used for attempts.

More importantly, internal/logstore/pglogstore/README.md:367-373 explicitly lists:

Easy data retention (drop old partitions)

as a benefit of the time-based partitioning design.

However, we could not find runtime or migration code that creates, attaches, detaches, or drops those partitions.

The retention documentation also appears unfinished: docs/content/self-hosting/guides/event-delivery-log.mdoc:8 currently contains:

Need to talk about data retention and retention policies.

Request

It would be great to complete the Postgres retention design by adding:

  1. Automatic time-range partition management — create future partitions and drop expired ones.
  2. A Postgres retention setting implemented on top of those partitions.
  3. A supported migration path for existing installations where data is already in the DEFAULT partitions.
  4. Documentation describing the intended Postgres retention model.

Questions

  1. Is Postgres partition lifecycle management already planned or tracked?
  2. Is there a recommended migration path for existing DEFAULT partitions?
  3. Until native retention exists, what retention approach do you recommend for Postgres?

Small unrelated finding

The primary-key index on attempts_default still appears to be named deliveries_default_pkey.

000005_denormalize_attempts.up.sql:59-60 renames the table and partition but apparently not the constraint-backing index. Harmless, but slightly confusing when inspecting pg_stat_user_indexes.

Lenguaje dominante
Go
Estrellas
1.1k
Forks
70
Merge medio
1 d 18 h
PR fusionados (30 d)
56

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de hookdeck/outpost

Todos los issues de hookdeck/outpost

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.