Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Is there any danger running /etc/init.d/postgresql restart?? We just had an incident where some relations “disappeared” and I ran the said command. Just got bollocked by the sysadmin, however he did not justify why this was a bad thing to do. I did put the webapp in maintenance mode so there wasn’t any transactions/ queries going on at the time.
Thanks guys… So in short it wont damage anything but it could loose lots of valuable diagnostic info.
No, there is no danger of restarting postgres using the init.d method.
However, to restart it because something weird happened is not a good idea, because it limits severely the amount of information you can collect to find the root cause and limits opportunities to fix it.
Also in all the years I have been involved with postgresql, I never encountered a situation in which a restart “fixed” the problem. The immediate ‘incident’ might be resolved but if there’s a problem, it will still be there.