> On 19. Jan, 2021, at 04:48, David G. Johnston <david.g.johnston@gmail.com> wrote: > > And now the standby is waiting for the next wal file to be archived by the primary. You should probably set archive_timeout to a non-zero value since the primary doesn’t seem very busy (though you also still need to do at least one write, empty wal files don’t get rotated out and archived.)
you should be able to get around your problem by doing the following on the primary database:
checkpoint; select pg_switch_wal();
The pg_switch_wal() alone will not trigger WAL file generation if no transaction has been going on. That's why I recommend forcing a checkpoint before that (same with Oracle by the way).
As soon as a WAL is generated, it should get shipped to the standby database. Then it should open.