Re: could not write to log -> PANIC -> System down - Mailing list pgsql-general

From Martijn van Oosterhout
Subject Re: could not write to log -> PANIC -> System down
Date
Msg-id 20061214222237.GG24370@svana.org
Whole thread Raw
In response to Re: could not write to log -> PANIC -> System down  ("Brandon Aiken" <BAiken@winemantech.com>)
Responses Re: could not write to log -> PANIC -> System down  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: could not write to log -> PANIC -> System down  ("Brandon Aiken" <BAiken@winemantech.com>)
List 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@svana.org>   http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.

Attachment

pgsql-general by date:

Previous
From: "Brandon Aiken"
Date:
Subject: Re: could not write to log -> PANIC -> System down
Next
From: Vlad
Date:
Subject: Re: Temp file space (Re: creating an index with tablespace on a dedicated filesystem)