From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: GIN fast insert |
Date: | 2009-02-11 04:51:31 |
Message-ID: | 603c8f070902102051w4c77d49aobbff46ffdb0d9780@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Feb 10, 2009 at 11:18 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> For queries that select only a single index entry, there might be some
> speed degradation, but a quick test suggests it's in the
> single-digit-percentage range if everything's cached; and of course if
> you have to go to disk then the extra CPU cycles to push a bitmap around
> are lost in the noise.
>
> In any case, as a wise man once said "I can make this code arbitrarily
> fast, if it doesn't have to give the right answer". Blowing up in easily
> foreseeable circumstances isn't my idea of giving the right answer.
Sure, but dropping index-scan support is not the only way of fixing
that problem. It has a certain elegance to it, but if it produces a
perceptible slowdown, it may not be the best approach.
...Robert
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Chernow | 2009-02-11 05:12:27 | Re: PQinitSSL broken in some use casesf |
Previous Message | Robert Haas | 2009-02-11 04:34:22 | Re: PQinitSSL broken in some use casesf |