Re: [PATCH] New [relation] option engine

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: Nikolay Shaplov <dhyan(at)nataraj(dot)su>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, Amit Langote <amitlangote09(at)gmail(dot)com>
Subject: Re: [PATCH] New [relation] option engine
Date: 2022-07-11 20:03:55
Message-ID: 72554626ddbb9ff1b8a218139fb2655d9fc5199a.camel@j-davis.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, 2022-02-14 at 00:43 +0300, Nikolay Shaplov wrote:
> For index access methods "amoptions" member function that preformed
> option
> processing, were replaced with "amreloptspecset" member function that
> provided
> an SpecSet for reloptions for this AM, so caller can trigger option
> processing
> himself.

What about table access methods? There have been a couple attempts to
allow custom reloptions for table AMs. Does this patch help that use
case?

Regards,
Jeff Davis

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2022-07-11 20:04:00 Re: automatically generating node support functions
Previous Message Tom Lane 2022-07-11 19:54:22 Re: automatically generating node support functions