Re: Reloptions for table access methods - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Reloptions for table access methods
Date
Msg-id CANP8+jLk9hs9UYEdnudi2QcrcOZ4X0ubFJk3_0-TKGDEv7wq6A@mail.gmail.com
Whole thread Raw
In response to Re: Reloptions for table access methods  (Jeff Davis <pgsql@j-davis.com>)
Responses Re: Reloptions for table access methods
List pgsql-hackers
On Tue, 1 Sept 2020 at 18:21, Jeff Davis <pgsql@j-davis.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/



pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: SQL/JSON: functions
Next
From: Fabrízio de Royes Mello
Date:
Subject: Re: Minimal logical decoding on standbys