| From: | Aleksander Alekseev <aleksander(at)tigerdata(dot)com> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Junwang Zhao <zhjwpku(at)gmail(dot)com>, Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>, Rafia Sabih <rafia(dot)pghackers(at)gmail(dot)com>, Julien Tachoires <julien(at)tachoires(dot)me> |
| Subject: | Re: Allow table AMs to define their own reloptions |
| Date: | 2026-09-07 12:41:32 |
| Message-ID: | CAJ7c6TOFr6ETF=JiUkWKGmPsuXB5uGumQLoBLHL6q9XL+c7hHg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Andrew,
> Attached is v7. Changes since v6:
>
> [...]
That's an important feature, thanks for driving it. We wanted
something like this in the recent commit 0e944fe3 but ended up using a
GUC.
There is one important design difference however. Your patch allows
given TAMs to have their own reloptions. In 0e944fe3 the task was
different. An extension that doesn't implement a TableAM should be
able to extend `CREATE TABLE foo WITH (...)` with its own options
independent of the underlying TAM. The way these options are
interpreted depends on the extension, not the underlying TAM.
If we could separate reloptions extension from TAM implementation that
would be much more flexible. Do you think it's possible?
--
Best regards,
Aleksander Alekseev
| From | Date | Subject | |
|---|---|---|---|
| Next Message | vignesh C | 2026-09-07 12:55:35 | Publication DDL can race with a concurrent UPDATE |
| Previous Message | Priyanka S | 2026-09-07 12:27:18 | Re: [PATCH] Planner support function for generate_subscripts() |