From: | Guillaume Cottenceau <gc(at)mnc(dot)ch> |
---|---|
To: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: planner with index scan cost way off actual cost, |
Date: | 2006-03-22 16:25:56 |
Message-ID: | 87irq6e99n.fsf@meuh.mnc.lan |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Hi Scott,
Scott Marlowe <smarlowe 'at' g2switchworks.com> writes:
> On Wed, 2006-03-22 at 02:04, Guillaume Cottenceau wrote:
[...]
> > Yes, we use 7.4.5 actually, because "it just works", so production
> > wants to first deal with all the things that don't work before
> > upgrading. I have recently discovered about the background writer
> > of 8.x which could be a supplementary reason to push for an
> > ugprade though.
>
> Imagine you get a call from the manufacturer of your car. There's a
> problem with the fuel pump, and, in a small percentage of accidents,
> your car could catch fire and kill everyone inside.
>
> Do you go in for the recall, or ignore it because you just want your car
> to "just work?"
Ah, this holy computer/OS/whatever-to-cars comparison.. How many
million electrons would the world save if computer people would
abandon it? :)
> In the case of the third number in postgresql releases, that's what
> you're talking about. the updates that have come after the 7.4.5
> version, just talking 7.4 series here, have included a few crash and
> data loss fixes. Rare, but possible.
I guess we didn't know that. I for myself have (a bit more)
excuses because I'm on the development side :) But I've passed
the information to the operation team, thank you.
--
Guillaume Cottenceau
From | Date | Subject | |
---|---|---|---|
Next Message | Luke Lonergan | 2006-03-22 17:10:58 | Re: Intel C/C++ Compiler Tests |
Previous Message | Csaba Nagy | 2006-03-22 16:19:58 | Re: WAL logging of SELECT ... INTO command |