Tom Lane <[EMAIL PROTECTED]> writes:
> If you want to force things to happen then you should send SIGINT to
> the postmaster, which in turn will SIGTERM its backends, which in
> theory will abort their transactions and shut down. (No, this isn't
> real consistent, but we wanted the right things
>
>Waiting for the next crash with anticipation...
Since you said you are running ACS is here you may as well want to
set the param Verbose to True in your db pool which will log all queries to
the db in the access log. Then when it crashes during
normal execution you can simple determine the o
Tom Lane <[EMAIL PROTECTED]> writes:
> Doug McNaught <[EMAIL PROTECTED]> writes:
> > From what I've seen so far, all the backends (other than the one that
> > actually crashes) seem to survive the SIGTERM I send to the
> > postmaster. How do I tell which one is which? The command line?
>
> SIG
Doug McNaught <[EMAIL PROTECTED]> writes:
> From what I've seen so far, all the backends (other than the one that
> actually crashes) seem to survive the SIGTERM I send to the
> postmaster. How do I tell which one is which? The command line?
SIGTERM to the postmaster commands polite shutdown, i
Tom Lane <[EMAIL PROTECTED]> writes:
> Doug McNaught <[EMAIL PROTECTED]> writes:
> > I'm running VACUUM, then VACUUM ANALYZE (the docs seem to suggest that
> > you need both). Basically my script is:
>
> VACUUM ANALYZE is a superset of VACUUM; you do not need both.
Good to know.
> > The exam
