Subject: Re: [PERFORM] Hints proposal
From: Csaba Nagy <nagy@ecircle-ag.com>
To: Andrew Sullivan <ajs@crankycanuck.ca>
Cc: postgres hackers <pgsql-hackers@postgresql.org>
In-Reply-To: <20061013140915.GC31912@phlogiston.dyndns.org>
References: <20061012174503.GA29203@phlogiston.dyndns.org>
	<E1539E0ED7043848906A8FF995BDA579016A0981@m0143.s-mxs.net>
	<20061013140915.GC31912@phlogiston.dyndns.org>
Content-Type: text/plain
Message-Id: <1160749207.28751.115.camel@coppola.muc.ecircle.de>
Mime-Version: 1.0
Date: Fri, 13 Oct 2006 16:20:08 +0200
Content-Transfer-Encoding: 7bit

> And remember, the places where PostgreSQL is getting used most
> heavily are still the sort of environments where people will take a
> lot of short cuts to achieve an immediate result, and be annoyed when
> that short cut later turns out to have been expensive.  Postgres will
> get a black eye from that ("Too hard to manage!  Upgrades cause all
> sorts of breakage!").

Those guys will do their shortcuts anyway, and possibly reject postgres
as not suitable even before that if they can't take any shortcuts.

And upgrades are always causing breakage, I didn't have one upgrade
without some things to fix, so I would expect people is expecting that.
And that's true for Oracle too, our oracle guys always have something to
fix after an upgrade. And I repeat, I always had something to fix for
postgres too on all upgrades I've done till now.

Cheers,
Csaba.