Thanks to everyone that provided input about this idea. After taking
everything into consideration and talking with Olly Betts from the
Xapian project, what I'm going to do is implement a btree that supports
multiple roots and an "tag" value of arbitrary length for each item in
the tree. Then
On Jan 2, 2004, at 4:54 PM, Alvaro Herrera wrote:
I think your approach is too ugly. You will have tons of problems the
minute you start thinking about concurrency (unless you want to allow
only a single user accessing the index)
It might be ugly, but it's very fast. Surprisingly fast, actually.
On Sat, Jan 03, 2004 at 02:49:23PM +0800, Christopher Kings-Lynne wrote:
> >I think one way of attacking the problem would be using the existing
> >nbtree by allowing it to store the five btrees.
>
> Why not write it using the GiST interface - that is after all the entire
> point of GiST...
Well
On Thu, Jan 01, 2004 at 11:19:07PM -0500, Eric B.Ridge wrote:
> I couldn't think of a way to create a whole new database type for
> Xapian that could deal with managing 5 btree indexes inside of Postgres
> (other than using tables w/ standard postgres btree index on certain
> fields), so instea
On Dec 26, 2003, at 4:04 PM, Tom Lane wrote:
Eric Ridge <[EMAIL PROTECTED]> writes:
Xapian has it's own storage subsystem, and that's what I'm using to
store the index... not using anything internal to postgres (although
this could change).
I would say you have absolutely zero chance of making it w
Eric Ridge <[EMAIL PROTECTED]> writes:
> I assume the doc chapter on Page Files and the various storage-related
> README files are good places for more information. Any other tips or
> pointers?
Not right offhand, but feel free to ask questions when you get stuck.
Also don't forget that there's
On Dec 26, 2003, at 4:04 PM, Tom Lane wrote:
Eric Ridge <[EMAIL PROTECTED]> writes:
Xapian has it's own storage subsystem, and that's what I'm using to
store the index... not using anything internal to postgres (although
this could change).
I would say you have absolutely zero chance of making it
Eric Ridge <[EMAIL PROTECTED]> writes:
> Xapian has it's own storage subsystem, and that's what I'm using to
> store the index... not using anything internal to postgres (although
> this could change).
I would say you have absolutely zero chance of making it work that way.
You will not be able t
On Dec 26, 2003, at 3:22 PM, Tom Lane wrote:
3) How does one get the $PGDATA directory?
DataDir. Why should you care? An index AM that wants to know this is
probably broken IMHO; it's certainly trying to do something that's
outside the charter of index AMs, and is likely to cause lots of
headache
Eric Ridge <[EMAIL PROTECTED]> writes:
> 1) Is it possible for an access method to receive some kind of "DROP
> INDEX" notification?
No.
> select * from test where stuff => 'stuff' AND NOT more_stuff =>
> '"drink beer"';
> has this plan:
To do better here, you'd need to invent a "not-=>'
(I started with this addressed to the -general list, but it just
doesn't seem like a general usage topic. If -hackers is the wrong
place, please point me in the right direction).
I've been working on a custom index type (access method) that allows
postgres to do fulltext searching (including p
11 matches
Mail list logo
