> > Well I certainly can't argue with that :) but it is a really hard
> > argument to make to the customer. These are customers who have spent
> > many more times your and my salaries on software and needed these
> > *repair* tools in the past.
>
> OK, so do we give them a /bin/true and go away? How do we address this?
>
Heh... Good question. We can't use the argument that we don't corrupt
stuff, cause it does happen. It may not be PostgreSQL's fault, it likely
isn't... but the end result is PostgreSQL is corrupted and needs to be
fixed.
The common way to do that is dump/reload whatever is bad or look for
specific rows etc...
What do you do when looking at a 300 million rows table? Outages just
are not that keen in today's world.
Sincerely,
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997 http://www.commandprompt.com/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
