- Newest
- Most votes
- Most comments
Hi, Annie Bai
I'm not seeing a solve for this in re:Post or on the internet. I wonder if the following two ideas could be tested on a Non Production (ideally, Sandbox) system ONLY - Please DO NOT Run Any of the Following on Production.
First, ensure you have a backup of /rdsdbdata/config/postgresql.conf. A backup of the file can be created using the following command.
Create Backup of file /rdsdbdata/config/postgresql.conf
cp -p /rdsdbdata/config/postgresql.conf /rdsdbdata/config/postgresql.conf.bkp
Step 1 - Create a symbolic link to the new config file name - this will create a file link (recovery.conf) pointing to postgresql.conf.
cd /rdsdbdata/config
ln -s postgresql.conf recovery.conf
or
Step 2 - Create empty file - you might need to run rm /rdsdbdata/config/recovery.conf first, if you ran Step 1 before this. The single command below will create an empty recovery.conf file.
touch /rdsdbdata/config/recovery.conf
If either of the two steps above work in a Sandbox (Non Production) environment, please choose this as the Accepted Answer so others on re:Post may benefit - Thank you
Relevant content
- asked 10 months ago
- asked a year ago
- asked 7 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago