| From: | Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org, Ajit Awekar <ajitpostgres(at)gmail(dot)com>, Aleksander Alekseev <aleksander(at)tigerdata(dot)com> |
| Subject: | Re: Allow table AMs to define their own reloptions |
| Date: | 2026-09-30 21:22:17 |
| Message-ID: | CAN4CZFMRjfFXW3Baczgra4ff7fTNiKBUXXZ5OfcJhWZ4-xrc1A@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
pg_dump has the option "--no-table-access-method". Should that somehow
interact with this feature? As currently that can result in non
restorable dumps.
There's also one more limitation similar to the TEXT issue I reported
upthread - and similarly it's not an issue for current tests, but
might be worth improving:
/* src: src/backend/access/heap/heapam.c:1449-1452 */
if (unlikely(sscan->rs_rd->rd_tableam != GetHeapamTableAmRoutine()))
ereport(ERROR, ... errmsg_internal("only heap AM is supported")));
CREATE TABLE ti (a int) USING dummy_table_am;
CREATE INDEX ON ti(a); -- ERROR:
only heap AM is supported
CREATE TABLE tp (a int PRIMARY KEY) USING dummy_table_am; -- ERROR:
only heap AM is supported
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Paul A Jungwirth | 2026-09-30 21:41:21 | WITHOUT OVERLAPS foreign key allows referencing EXCLUDE constraint |
| Previous Message | Tom Lane | 2026-09-30 21:01:05 | Re: Do we need to back-patch tzcode 2026b after all? |