Re: could not write to log -> PANIC -> System down

From: Martijn van Oosterhout <kleptog(at)svana(dot)org>
To: Brandon Aiken <BAiken(at)winemantech(dot)com>
Cc: Merlin Moncure <mmoncure(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: could not write to log -> PANIC -> System down
Date: 2006-12-14 22:22:37
Message-ID: 20061214222237.GG24370@svana.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Dec 14, 2006 at 05:13:30PM -0500, Brandon Aiken wrote:
> Of course, it's Windows. "Should not" is often a suggestion, it seems.
> As a port, postmaster.exe was presumably not written with VSS in mind,
> so it might object to the shadow copy instantiation (which, again, it
> *should* not be able to do).

Any backup system that is not transparent to processes running on the
system seems to be flawed by design.

> No idea on the frequent autovacuuming. Do you do a lot of deletes?

In those messages "processing" just means it woke up to see if there
was anything to do. It probably didn't do anything. Waking up every
minute is not that big a deal...

Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Vlad 2006-12-14 22:51:54 Re: Temp file space (Re: creating an index with tablespace on a dedicated filesystem)
Previous Message Brandon Aiken 2006-12-14 22:13:30 Re: could not write to log -> PANIC -> System down