Re: [HACKERS] Checkpoint request failed on version 8.2.1.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Jim C(dot) Nasby" <jim(at)nasby(dot)net>
Cc: Patrick Earl <patearl(at)patearl(dot)net>, pgsql-general(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] Checkpoint request failed on version 8.2.1.
Date: 2007-01-11 21:32:42
Message-ID: 5739.1168551162@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

"Jim C. Nasby" <jim(at)nasby(dot)net> writes:
> Given that this could result in data loss, if this was to be done I'd
> very much want to see a way to disable it in a production environment.

Production environments are the same ones that won't be happy with
random checkpoint failures, either.

If we can't find a way to positively identify the deleted-file failures
then I think we've got to do something like this.

(You know, of course, that my opinion is that no sane person would run a
production database on Windows in the first place. So the data-loss
risk to me seems less of a problem than the unexpected-failures problem.
It's not like there aren't a ton of other data-loss scenarios in that OS
that we can't do anything about...)

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2007-01-11 21:35:08 Re: ORDER BY col is NULL in UNION causes error?
Previous Message Richard P. Welty 2007-01-11 21:30:59 documentation vs reality: template databases

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2007-01-11 21:38:30 Re: [HACKERS] Checkpoint request failed on version 8.2.1.
Previous Message Jim C. Nasby 2007-01-11 21:26:10 Problem linking libecpg.5.3.dylib on OS X