I've noticed that if for example the autovacuum process dies (such as
with a kill -9 when testing my new shared mem implementation), only
autovac and bgwriter are restarted. The stats collector is terminated,
but not restarted. (Same goes for a regular backend, and not just
autovac)
Is there a
Magnus Hagander wrote:
I've noticed that if for example the autovacuum process dies (such as
with a kill -9 when testing my new shared mem implementation), only
autovac and bgwriter are restarted. The stats collector is terminated,
but not restarted. (Same goes for a regular backend, and not
On Tue, Mar 20, 2007 at 08:48:30AM -0400, Alvaro Herrera wrote:
Magnus Hagander wrote:
I've noticed that if for example the autovacuum process dies (such as
with a kill -9 when testing my new shared mem implementation), only
autovac and bgwriter are restarted. The stats collector is
Alvaro Herrera [EMAIL PROTECTED] writes:
Magnus Hagander wrote:
I've noticed that if for example the autovacuum process dies (such as
with a kill -9 when testing my new shared mem implementation), only
autovac and bgwriter are restarted. The stats collector is terminated,
but not restarted.
Magnus Hagander [EMAIL PROTECTED] writes:
Bah, sorry about the noise. It was the effect of
PGSTAT_RESTART_INTERVAL.
Do we want to add some logging when we don't restart it due to repeated
failures?
Not really, but maybe it would be sensible to reset last_pgstat_start_time
when doing a
