On 10/4/21 12:35, Dennis Jacobfeuerborn wrote:
Hi,
I just stopped and restarted a Postgres 11 docker container which so far
has happily streamed the WAL from its primary but after the restart it
now seems to completely ignore the recovery.conf file and just outputs
this:
2021-10-04 10:14
That happened with Postgres 12 I think so it shouldn't affect this
installation.
On 10/4/21 12:40, Josef Šimánek wrote:
Isn't this related to merge into postgresql.conf
(https://www.postgresql.org/docs/current/recovery-config.html)?
po 4. 10. 2021 v 12:35 odesílatel Dennis Jaco
Hi,
I just stopped and restarted a Postgres 11 docker container which so far
has happily streamed the WAL from its primary but after the restart it
now seems to completely ignore the recovery.conf file and just outputs this:
2021-10-04 10:14:19.103 UTC [1] LOG: listening on IPv4 address
"0.
On 11/13/20 4:02 PM, Tom Lane wrote:
> Dennis Jacobfeuerborn writes:
>> All of this works fine and the logs report that the db reaches a
>> consistent recovery state but as last entry it reports an "invalid
>> record length":
>
> This looks quite normal to m
Hi,
I've run into a strange issue after restoring a backup that I created
using pg_basebackup on a standby instance. The command I use to create
the backup is this:
pg_basebackup -v --write-recovery-conf -h$BACKUP_HOST -p5432
-U$BACKUP_USER --format tar --wal-method stream --compress=2 -D
"$BACKUP
Hi,
I'm currently trying to understand how backups work. In the
documentation in section "25.2. File System Level Backup" it says that
filesystem level backups can only be made when the database if offline
yet pg_basebackup seems to do just that but works while the database is
online. Am I misunder
