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

Replication woes

Abierto
#713 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
25/100
Tipo de issue
Documentación
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
linux, macos, postgresql

Línea de trabajo

No files or tests are named. Start by reviewing how PostgresApp handles data directories and the PostgreSQL log shipping replication approach described in the issue, then determine whether migration in both directions is supported. Done means documenting a verified migration and replication path, or clearly stating the limitations and unsupported steps.

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

Descripción

Hi there ... having a really hard time replicating from a Linux postgres setup to Postgress.app. I've tried a few different approaches but none have worked so far, so looking for advice or possibly documentation ... here's the methods I've tried:

  1. Copy over from current master using pg_basebackup to an appropriately located directory (~/Library/Application Support/Postgres/blah) -- PostgresApp does not pick up on this new directly.
  2. tried then making a new DB at that location, still doesn't pick up, wants to initialize a new DB, doing so will make the new DB but it will not pickup the current data that's there.
  3. Another attempt was to first initialize a new DB through app interface and then us pg_basebackup. This would not work because pb_basebackup wants an empty target (pg_basebackup: error: directory "/Users/mguertin/Library/Application Support/Postgres/v15_production" exists but is not empty)
  4. Tried a combination of the two, made a new DB in the PostressApp UI, used pg_basebackup to copy to a different dir and then tried to cherry pick the things that PostgressApp was looking for and combining those two. PostgressApp still wants to initialize, so I'm assuming I'm missing on moving something that it requires.

Is there any known way to make these two play nicely together for replication? I'm looking to migrate my current production (linux) over to PostrgresApp on macos, and after that migration still have PostgressApp replicate back to the linux instance. If it matters I'm using log shipping replication right now between multiple linux hosts. If it's possible to do what I'm looking to do it would be awesome to have a bit of documentation on how this could all work, even if it's just a basic overview!

Thanks in advance and love this app, makes life a lot easier. Hoping I can use this and not have to go back to homebrew on macos.

Lenguaje dominante
Makefile
Estrellas
7.8k
Forks
404
Merge medio
6 h 55 min
PR fusionados (30 d)
6

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

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 PostgresApp/PostgresApp

Todos los issues de PostgresApp/PostgresApp

Issues similares

Más issues de Databases

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.