Skip site navigation (1) Skip section navigation (2)

Re: rbtree code breaks GIN's adherence to maintenance_work_mem

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: rbtree code breaks GIN's adherence to maintenance_work_mem
Date: 2010-07-31 16:44:46
Message-ID: 2298.1280594686@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Sat, Jul 31, 2010 at 12:32 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> So it'd definitely be a lot better than now. Maybe there'd be some
>> remaining performance gap for non-pathological cases, but I think we
>> would be willing to pay that in order to avoid bad behavior for the
>> pathological cases. It's difficult to say for sure of course
>> without going to the trouble of coding and testing it.

> Well, it sounds like a reasonable thing to try, then.  You going to
> take a crack at it?

Yeah, I'll have at it.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Robert HaasDate: 2010-07-31 17:32:13
Subject: Re: ANALYZE versus expression indexes with nondefault opckeytype
Previous:From: Robert HaasDate: 2010-07-31 16:34:55
Subject: Re: rbtree code breaks GIN's adherence to maintenance_work_mem

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group