pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Carlos Moreno <moreno_pg@mochima.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: View is not using a table index
Date: Tue, 24 Apr 2007 17:13:59 -0400
Message-ID: <462E7317.2070707@mochima.com> (raw)
In-Reply-To: <6365.1177438176@sss.pgh.pa.us>
References: <75312DFA648AF74D8A236E5269BFBE4B04292F00@ncrx3.ncr.int.ec.gc.ca>
	<462E2537.2020706@archonet.com>
	<75312DFA648AF74D8A236E5269BFBE4B04292F02@ncrx3.ncr.int.ec.gc.ca>
	<6365.1177438176@sss.pgh.pa.us>

Tom Lane wrote:
> Dan Shea <dan.shea@ec.gc.ca> writes:
>   
>> You make it sound so easy.  Our database size is at 308 GB.
>>     
>
> Well, if you can't update major versions that's understandable; that's
> why we're still maintaining the old branches.  But there is no excuse
> for not running a reasonably recent sub-release within your branch.
> Read the release notes, and consider what you will say if one of the
> several data-loss-causing bugs that were fixed long ago eats your DB:
>   

Was it Feb 2002?  The Slammer effectively shut down the entire Internet,
due to a severe bug in Microsucks SQL Server...  A fix for that buffer
overflow bug had been available since August 2001;  yet 90% of all SQL
servers on the planet were unpatched.

As much as it pains me to admit it, the lesson about the importance of
being a conscious, competent administrator takes precedence over the
lesson of how unbelievably incompetent and irresponsible and etc. etc.
Microsoft is to have such a braindead bug in such a high-profile and
high-price product.

Tom said it really nicely --- do stop and think about it;  the day arrives
when you *lost* all those 308 GB of valuable data;  and it was only in
your hands to have prevented it!  Would you want to see the light of
*that* day?

Carlos
--




view thread (6+ messages)

Message-ID: <462E7317.2070707@mochima.com>
Permalink:  ../462E7317.2070707@mochima.com/
Also on:    postgresql.org/message-id/462E7317.2070707@mochima.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: moreno_pg@mochima.com
  Subject: Re: View is not using a table index
  In-Reply-To: <462E7317.2070707@mochima.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox