Hi,
The genericcostestimate function is currently static. This limits the
development of new access methods as loadable modules without touching
pgsql sources. Currently I have to include a copy of the function in the
module, which is obviously too bad.
Is there any reason to keep this function
Tom Lane wrote:
"Ramy M. Hassan" <[EMAIL PROTECTED]> writes:
The genericcostestimate function is currently static. This limits the
development of new access methods as loadable modules without touching
pgsql sources. Currently I have to include a copy of the function in the
Hi all,
Is there any updated implementation guide for postgresql 7.x ? I've been
using the postgres95 guide at http://pluto.iis.nsk.su/postgres95/impl-guide/
but it is incomplete and also it does not reflect the current state of the
code. I can see many structures were modified since postgres95
ovember 10, 2004 12:35 AM
To: Ramy M. Hassan; Pgsql Hackers
Cc: Teodor Sigaev; Walid G. Aref
Subject: Re: sp-gist porting to postgreSQL
Ramy,
glad to hear from you !
AFAIK, posgresql doesnt' supports several indices for the same type.
I think this is a problem of optimizer. Probably other hackers
would
appreciate your opinions regarding to this design issue.
Thanks
Ramy
-Original Message-
From: Oleg Bartunov [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 10, 2004 5:21 AM
To: Ramy M. Hassan
Cc: 'Pgsql Hackers'; 'Teodor Sigaev'; 'Walid G. Aref'
S
On Wed, 10 Nov 2004, Oleg Bartunov wrote:
On Wed, 10 Nov 2004, Ramy M. Hassan wrote:
I believe that it is still possible to have several index access methods
for
the same type and the same operations. But this requires that each index
access method has its own tuple in the pg_am relation and
