From: Csaba Nagy <nagy@ecircle-ag.com>
To: Andrew Sullivan <ajs@crankycanuck.ca>
Cc: postgres hackers <pgsql-hackers@postgresql.org>
Subject: Re: [PERFORM] Hints proposal
Date: Fri, 13 Oct 2006 16:20:08 +0200
Message-ID: <1160749207.28751.115.camel@coppola.muc.ecircle.de> (raw)
In-Reply-To: <20061013140915.GC31912@phlogiston.dyndns.org>
References: <20061012174503.GA29203@phlogiston.dyndns.org>
<E1539E0ED7043848906A8FF995BDA579016A0981@m0143.s-mxs.net>
<20061013140915.GC31912@phlogiston.dyndns.org>
> 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.
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: nagy@ecircle-ag.com, ajs@crankycanuck.ca, pgsql-hackers@postgresql.org
Subject: Re: [PERFORM] Hints proposal
In-Reply-To: <1160749207.28751.115.camel@coppola.muc.ecircle.de>
* 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