From: Mark Kirkwood <mark.kirkwood@catalyst.net.nz>
To: pgsql-performance@postgresql.org
Subject: Re: Talking about optimizer, my long dream
Date: Sat, 05 Feb 2011 12:44:19 +1300
Message-ID: <4D4C8F53.8090804@catalyst.net.nz> (raw)
In-Reply-To: <4D4C0EDA.8000704@vmsinfo.com>
References: <AANLkTikMbdPKq_pgihiUOWRnR3eSsn0B1vjMKonq1QrL@mail.gmail.com>
<4D4C0590.1050609@vmsinfo.com>
<4D4C0702.1040909@peak6.com>
<4D4C0EDA.8000704@vmsinfo.com>
On 05/02/11 03:36, Mladen Gogala wrote:
> Shaun, I don't need to convince you or the Postgres community. I
> needed an argument to convince my boss.
> My argument was that the sanctimonious and narrow minded Postgres
> community is unwilling to even consider creating the tools I need for
> large porting projects, tools provided by other major databases. This
> discussion served my purpose wonderfully. Project is killed, here we
> part ways. No more problems for either of us. Good luck with the
> "perfect optimizer" and good riddance. My only regret is about the
> time I have wasted.
>
I think it is unlikely that your boss is going to dismiss Postgres on
the basis of some minor technical point (no optimizer hints). Bosses
usually (and should) care about stuff like reference sites, product
pedigree and product usage in similar sized companies to theirs.
Postgres will come out rather well if such an assessment is actually
performed I would think.
The real question you should be asking is this:
Given that there are no hints, what do I do to solve the problem of a
slow query suddenly popping up in production? If and when this situation
occurs, see how quickly the community steps in to help you solve it (and
it'd bet it will solved be very quickly indeed).
Best wishes
Mark
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: mark.kirkwood@catalyst.net.nz
Subject: Re: Talking about optimizer, my long dream
In-Reply-To: <4D4C8F53.8090804@catalyst.net.nz>
* 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