| From: | Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com> |
|---|---|
| To: | |
| 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:25:40 |
| Message-ID: | CAEze2WgAv8yXnJg5tuJ=oBB7HtphHY6KzZUbWHiOAq_ZsSCv5w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> PS. I noticed this when checking the sortsupport code for some active
> patches, and after playing around a bit while trying to run PG
> extensions that are not system-registered. The attached test case
> fails, where I'd expect it to succeed, or at least I expected it not
> to fail at "This AM's OID has an unexpected value".
I just realised that the failure of the specific mentioned test case
was unrelated to the issue at hand, as it correctly shows that you
can't use int8-opclasses for int4 columns.
The attached fixes that test case by creating a table with a bigint
column instead, so that the test correctly, but unexpectedly, outputs
"ERROR: unexpected non-btree AM: NNNNN".
- Matthias
| Attachment | Content-Type | Size |
|---|---|---|
| scratch_33.sql | application/octet-stream | 658 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2022-06-24 14:29:06 | Re: PG 15 (and to a smaller degree 14) regression due to ExprEvalStep size |
| Previous Message | Matthias van de Meent | 2022-06-24 14:17:06 | Pre-installed index access methods cannot be manually installed. |