From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Denis Perchine <dyp(at)perchine(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Quite strange crash |
Date: | 2001-01-09 06:23:26 |
Message-ID: | 101.979021406@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Denis Perchine <dyp(at)perchine(dot)com> writes:
> Hmmm... actually this is real problem with vacuum lazy. Sometimes it
> just do something for enormous amount of time (I have mailed a sample
> database to Vadim, but did not get any response yet). It is possible,
> that it was me, who killed the backend.
Killing an individual backend with SIGTERM is bad luck. The backend
will assume that it's being killed by the postmaster, and will exit
without a whole lot of concern for cleaning up shared memory --- the
expectation is that as soon as all the backends are dead, the postmaster
will reinitialize shared memory.
You can get away with sending SIGINT (QueryCancel) to an individual
backend. Anything else voids the warranty ;=)
But, having said that --- this VACUUM process had only been running
for two minutes of real time. Seems unlikely that you'd have chosen
to kill it so quickly.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Mikheev, Vadim | 2001-01-09 06:26:43 | RE: Quite strange crash |
Previous Message | Denis Perchine | 2001-01-09 06:13:29 | Re: Quite strange crash |