On Thu, Jun 16, 2005 at 07:15:08PM -0700, Todd Landfried wrote:
> Thanks for the link. I'll look into those.
>
> I'm going only on what my engineers are telling me, but they say
> upgrading breaks a lot of source code with some SQL commands that are
> a pain to hunt down and kill. Not sure if that's true, but that's
> what I'm told.
This is true. Migrating to a newer version is not a one-day thing. But
increasing shared_buffers is trivially done, would get you lots of
benefit, and it's very unlikely to break anything. (Migrating one
version can be painful already -- migrating three versions on one shot
might be a nightmare. OTOH it's much better to pay the cost of
migration once rather than three times ...)
--
Alvaro Herrera (<alvherre[a]surnet.cl>)
"The Postgresql hackers have what I call a "NASA space shot" mentality.
Quite refreshing in a world of "weekend drag racer" developers."
(Scott Marlowe)
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
