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:1
On Mon, Oct 04, 2021 at 12:35:48PM +0200, 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 t
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 Jacobfeuerborn
naps
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 Jacobfeuerborn
napsal:
>
> Hi,
> I just stopped and restarted a Postgres 11 docker container which so far
> has happily streamed the WAL from i
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.