Re: hot standby in Postgresql 12

As David highlighted,
>> I took the error from the cp command to mean that this was in fact a
warm standby regardless of any claims by the poster. I’ll readily admit I
am not that familiar with this stuff though.
Seems your archive command is not working properly. Set it first and then
try again.
Also, please share your postgresql.auto.conf ( remove confidential
information like - password , username , IP etc. , if any)

Regards
Rajni

On Wed, Jan 20, 2021 at 2:11 AM David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:

> On Tuesday, January 19, 2021, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
> wrote:
>
>>
>> > > cp: cannot stat '/u01/archive/000000030000000000000035': No such file
>> or directory
>> > > 2021-01-18 07:31:01.043 UTC [21079]LOG: started streaming WAL from
>> primary at 0/35000000 on timeline 3
>> > >
>> >
>> > 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.)
>>
>> If the standby is *streaming* WAL, it is *not* waiting for a WAL segment
>> to be archived.
>> WAL is streamed to the standby right away.
>>
>
> I took the error from the cp command to mean that this was in fact a warm
> standby regardless of any claims by the poster. I’ll readily admit I am
> not that familiar with this stuff though.
>
> David J.
>
>