Re: knngist patch support

From: Joshua Tolley <eggyknap(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: knngist patch support
Date: 2010-02-13 19:03:16
Message-ID: 4b76f787.9613f30a.6a24.ffff9209@mx.google.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Feb 13, 2010 at 01:31:44PM -0500, Robert Haas wrote:
> On Sat, Feb 13, 2010 at 1:28 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > Teodor Sigaev <teodor(at)sigaev(dot)ru> writes:
> >> I see your point. May be it's better to introduce new system table? pg_amorderop
> >> to store ordering operations for index.
> >
> > We could, but that approach doesn't scale to wanting more categories
> > in the future --- you're essentially decreeing that every new category
> > of opclass-associated operator will require a new system catalog,
> > along with all the infrastructure needed for that.  That guarantees
> > that the temptation to take shortcuts will remain high.
>
> Yeah. PFA a patch to allow 5-key syscaches.

(Realizing I'm a lurker in this conversation, and hoping not to ask irritating
questions) Do we need to rename SearchSysCache et al. to SearchSysCache1,
etc.? It seems to me that requires changes to all kinds of software without
any real need. The four lines of PL/LOLCODE that inspired this thought aren't
themselves a great burden, but when combined with everyone else using
SearchSysCache already...

--
Joshua Tolley / eggyknap
End Point Corporation
http://www.endpoint.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2010-02-13 19:12:22 Re: knngist patch support
Previous Message Robert Haas 2010-02-13 18:31:44 Re: knngist patch support