Matthias van de Meent <boekewurm+postgres@gmail.com> writes:
> Although it makes sense to ensure that we don't accidentally call such
> functions from the 'wrong location', it does mean that a user cannot
> manually install the preinstalled access methods and get a working
> index AM, because the internal code is checking the OID of the
> supplied relation's access method, which will not match the expected
> value when manually installed.
This seems like a straw argument, considering that there would be
dozens of other problems in the way of removing or replacing any
built-in index AMs.
> Is this expected? Would we accept patches that remove or reduce the
> impact of these artificial limitations?
Seems like a significant waste of effort to me.
regards, tom lane
