| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Reloptions for table access methods |
| Date: | 2020-12-15 17:37:32 |
| Message-ID: | CANP8+jLk9hs9UYEdnudi2QcrcOZ4X0ubFJk3_0-TKGDEv7wq6A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 1 Sept 2020 at 18:21, Jeff Davis <pgsql(at)j-davis(dot)com> wrote:
> I went with the simple approach because fixing that problem seemed a
> bit over-engineered. Here are some thoughts on what we could do:
The simple patch is admirable, but not something we should put into core.
I definitely don't agree with the premise that all existing heap
options should be common across all new or extension tableAMs. There
are dozens of such options and I don't believe that they would all
have meaning in all future storage plugins.
I think options should just work exactly the same for Indexes and Tables.
--
Simon Riggs http://www.EnterpriseDB.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabrízio de Royes Mello | 2020-12-15 18:24:38 | Re: Minimal logical decoding on standbys |
| Previous Message | Pavel Stehule | 2020-12-15 17:36:36 | Re: SQL/JSON: functions |