From: | Ben <bench(at)silentmedia(dot)com> |
---|---|
To: | "Randal L(dot) Schwartz" <merlyn(at)stonehenge(dot)com> |
Cc: | Postgresql-General General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Oracle purchases Sleepycat - is this the "other shoe" |
Date: | 2006-02-15 21:02:03 |
Message-ID: | Pine.LNX.4.64.0602151300400.1276@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Well, in all fairness, MySQL probably gives the right answer most of the time,
always really fast (except for some use cases).
On Wed, 15 Feb 2006, Randal L. Schwartz wrote:
>>>>>> "Tom" == Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>
> Tom> * Change to use no page locks for table scanning operations.
> Tom> Maybe I'm misunderstanding, but that sure sounds like they intend to
> Tom> dumb down BDB so that it no longer works well in concurrent situations,
> Tom> in order to save a few cycles in single-user scenarios. Have MySQL
> Tom> officially abandoned the multi-user case to us?
>
> What they lose in usability, they gain back in benchmarks, and that's
> all that matters: getting the wrong answer really fast.
>
> --
> Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
> <merlyn(at)stonehenge(dot)com> <URL:http://www.stonehenge.com/merlyn/>
> Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
> See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org
>
From | Date | Subject | |
---|---|---|---|
Next Message | Joachim Wieland | 2006-02-15 21:08:09 | Re: switch / case in plpgsql functions |
Previous Message | Richard Huxton | 2006-02-15 20:58:51 | Re: Connecting process to PostgreSQL works stunningly slow |