From: | "Chad" <chadzakary(at)hotmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: I see this as the end of BDB in MySQL without a doubt. |
Date: | 2006-02-16 10:57:34 |
Message-ID: | 1140087454.114772.181360@z14g2000cwz.googlegroups.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
TJ,
I will go back and study the PG backend API (its been a while since I
last looked at it) and get back to you. I was assuming rather than
stating that it didnt meet my needs. Do you have a link to its docs?
BDBs basic C API is what I am talking about and particularly the
abililty for fine grained seeking along leaf nodes, even by row number
in certain types of BTrees.
Ciaran
I am quite happy with the c-language API for postgres, as far as it's
> capabilities and access to low-level postgres. OK, the docs and examples could
> be better. Am I missing something in Chad's comments/warnings or is he
> missing something in not understanding pg better?
> Chad, could you say more about what in the BDB/API is missing and needed in postgres?
>
> TJ O'Donnell
> http://www.gnova.com/
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org
From | Date | Subject | |
---|---|---|---|
Next Message | Alban Hertroys | 2006-02-16 11:27:22 | NULLs in unique indexes; Was: Oracle purchases Sleepycat - is this the "other shoe" for MySQL AB? |
Previous Message | Bart Golda | 2006-02-16 09:56:30 | Re: Connecting process to PostgreSQL works stunningly slow |