From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Pre-installed index access methods cannot be manually installed. |
Date: | 2022-06-24 14:43:19 |
Message-ID: | 356221.1656081799@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Matthias van de Meent <boekewurm+postgres(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2022-06-24 14:59:25 | Re: making relfilenodes 56 bits |
Previous Message | Andrew Dunstan | 2022-06-24 14:29:06 | Re: PG 15 (and to a smaller degree 14) regression due to ExprEvalStep size |