Re: Index AM API changes for deferability - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Index AM API changes for deferability
Date
Msg-id 13888.1247638130@sss.pgh.pa.us
Whole thread Raw
In response to Index AM API changes for deferability  (Jeff Davis <pgsql@j-davis.com>)
Responses Re: Index AM API changes for deferability
List pgsql-hackers
Jeff Davis <pgsql@j-davis.com> writes:
> So, should we proceed assuming an index AM API change, or try to avoid
> it? If we should change the AM API, is Dean's API change acceptable?

There is no reason at all to avoid an index AM API change if one is
useful.  If you look at the history, we tend to change that API every
release or two anyway.

Whether this particular design is good is a different question, and
I don't have time right now to think about that.  But please don't
bend the system out of shape just to avoid an API change.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: [PATCH 3/3] Document geqo_seed variable.
Next
From: Peter Eisentraut
Date:
Subject: Re: CommitFest 2009-07 is Now Closed