- Le plus récent
- Le plus de votes
- La plupart des commentaires
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
Contenus pertinents
- demandé il y a un an
- demandé il y a 2 mois
- demandé il y a 4 mois
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a un an