Thanks a lot for your advice. I did it the same way you mentioned. Please share if it has any pull off.
Dear John,
One of the main reason behind it is majorly Security. Can you help me with the effects of doing so.
Thanks & Regards,
Devendra
Changing the name or disabling postgres is not going to have any appreciable impact on improving security - in fact, you run the risk of reducing security and potentially introducing other problems because you are going to make your environment bespoke and possibly more complex to work with. Many security weaknesses are the result of simple admin errors rather than due to 'evit doers' attacking your system. Bottom line is that all your database administrator accounts need to be hardened and secure regardless of what name is used. By changing the name, you run the risk that the account won't be included in audits and other security checks or administrators will not recognise the level of sensitivity which should be applied to the account. Far better off to use the standard account, but make sure it is locked down with multiple layers of security.
