Re: hot standby in Postgresql 12

log files ;

2021-01-18 07:31:00.946 UTC [21072]LOG: database system was interrupted;
last known up at 2021-01-18 07:30:07 UTC
cp: cannot stat '/u01/archive/00000004.history': No such file or directory
2021-01-18 07:31:00.963 UTC [21072]LOG: entering standby mode
2021-01-18 07:31:00.966 UTC [21072]LOG: restored log file
"00000003.history" from archive
2021-01-18 07:31:00.981 UTC [21072]LOG: restored log file
"000000030000000000000034" from archive
2021-01-18 07:31:01.029 UTC [21072]LOG: redo starts at 0/34000028
2021-01-18 07:31:01.030 UTC [21072]LOG: consistent recovery state
reached at 0/34000138
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
2021-01-18 07:31:10.242 UTC postgres postgres [21082]FATAL: the database
system is starting up
2021-01-18 07:53:42.915 UTC postgres postgres [21160]FATAL: the database
system is starting up

On Tue, Jan 19, 2021 at 9:01 AM David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:

> On Monday, January 18, 2021, Ankush Chawla <ankushchawla03(at)gmail(dot)com>
> wrote:
>
>> Preparing hot standby in PostgreSQL 12
>>
>> I have created a standby.signal file and added the parameter
>> hot_standby='on' in postgresql.conf file but i am still not able to query
>> the standby database
>> Database is not getting open for reading.
>>
>> postgres(at)ip-172-31-31-150:/u01/db10/pg_wal> psql -p 5490
>> psql: error: FATAL: the database system is starting up
>>
>>
> The database is starting up, this is expected. You need to consult the
> server logs for relevant information pertaining to the startup/restore
> process.
>
> David J.
>
>

--
Best Regards,
Ankush Chawla