Re: Planned changes to pg_am catalog

On Fri, 13 Jul 2001, Tom Lane wrote:

> Since I am about to add a "bulk delete" routine to the index access
> method APIs for concurrent VACUUM, I need to add a column to pg_am
> to define the associated procedure for each index AM.  This seems like
> a fine time to clean up some of the other outstanding TODO items for
> pg_am:
>
> Note that this doesn't address Oleg's concerns about haskeytype,
> lossiness, etc.  AFAICS those issues are not related to the contents
> of pg_am.  Later on, I am going to have some proposals for altering
> pg_opclass and related tables to deal with those issues...

Any chance you'd untie a knot for our development in 7.2 development
cycle ? Our code for multikey GiST, Btree is more or less complete
and work with ugly workaround, and the only thing we need is a
solution of the problem with index_formtuple.

>
> Comments?  Any other festering problems in this immediate area?
>
>             regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
>     (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
>
Regards,    Oleg
_____________________________________________________________
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow University (Russia)
Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/
phone: +007(095)939-16-83, +007(095)939-23-83