It's become clear I need to go back and rethink my logic for this
functionality. Thanks for all of the suggestions.
-- John
On Sat, Aug 25, 2012 at 12:40 AM, Chris Angelico ros...@gmail.com wrote:
On Sat, Aug 25, 2012 at 8:25 AM, John D. West john.d.w...@asu.edu wrote:
I *think* my
On Sat, Aug 25, 2012 at 8:25 AM, John D. West john.d.w...@asu.edu wrote:
I *think* my independent processes are cleaning up in that they supposedly
abort themselves if they lose db connection, but on restart there is a table
of pid's I'd like to (1) make sure all of the processes are really
Sometimes the server process crashes and restarts, usually when I run some
large calculations that eat up all available memory. Is there any way to
detect this and run a cleanup routine when it happens? Running 8.4 on
Ubuntu.
-- John
John D. West john.d.w...@asu.edu wrote:
Sometimes the server process crashes and restarts, usually when I
run some large calculations that eat up all available memory.
You might want to reconfigure to avoid that.
Is there any way to detect this and run a cleanup routine when it
happens?
I have various background processes outside of postgres that need to be
killed and restarted after the server reboots.
-- John
On Fri, Aug 24, 2012 at 2:29 PM, Kevin Grittner kevin.gritt...@wicourts.gov
wrote:
John D. West john.d.w...@asu.edu wrote:
Sometimes the server process
On 08/24/2012 03:46 PM, John D. West wrote:
I have various background processes outside of postgres that need to be
killed and restarted after the server reboots.
-- John
On Fri, Aug 24, 2012 at 2:29 PM, Kevin Grittner
kevin.gritt...@wicourts.gov mailto:kevin.gritt...@wicourts.gov
John D. West john.d.w...@asu.edu wrote:
I have various background processes outside of postgres that need
to be killed and restarted after the server reboots.
All of our applications are coded such that when they have an error
on a database connection, they check for a serialization failure
I *think* my independent processes are cleaning up in that they supposedly
abort themselves if they lose db connection, but on restart there is a
table of pid's I'd like to (1) make sure all of the processes are really
dead, killing any who aren't (2) reset flags in a table showing the status
of
