pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Nikolay Shaplov <dhyan@nataraj.su>
To: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
To: Jeff Davis <pgsql@j-davis.com>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Michael Paquier <michael@paquier.xyz>
Cc: Amit Langote <amitlangote09@gmail.com>
Subject: Re: [PATCH] New [relation] option engine
Date: Tue, 12 Jul 2022 07:30:40 +0300
Message-ID: <1823308.yXV3o4JbTB@thinkpad-pgpro> (raw)
In-Reply-To: <72554626ddbb9ff1b8a218139fb2655d9fc5199a.camel@j-davis.com>
References: <3766675.7eaCOWfIcx@thinkpad-pgpro>
	<72554626ddbb9ff1b8a218139fb2655d9fc5199a.camel@j-davis.com>

В письме от понедельник, 11 июля 2022 г. 23:03:55 MSK пользователь Jeff Davis 
написал:

> > 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?

This patch does not add custom reloptions for table AM. It is already huge 
enough, with no extra functionality. But new option engine will make adding 
custom options for table AM more easy task, as main goal of this patch is to 
simplify adding options everywhere they needed. And yes, adding custom table 
AM options is one of my next goals, as soon as this patch is commit.

-- 
Nikolay Shaplov aka Nataraj
Fuzzing Engineer at Postgres Professional
Matrix IM: @dhyan:nataraj.su

Attachments:

  [application/pgp-signature] signature.asc (487B, ../1823308.yXV3o4JbTB@thinkpad-pgpro/2-signature.asc)
  download

view thread (42+ messages)  latest in thread

Message-ID: <1823308.yXV3o4JbTB@thinkpad-pgpro>
Permalink:  ../1823308.yXV3o4JbTB@thinkpad-pgpro/
Also on:    postgresql.org/message-id/1823308.yXV3o4JbTB@thinkpad-pgpro

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: dhyan@nataraj.su, pgsql-hackers@lists.postgresql.org, pgsql@j-davis.com, alvherre@2ndquadrant.com, michael@paquier.xyz, amitlangote09@gmail.com
  Subject: Re: [PATCH] New [relation] option engine
  In-Reply-To: <1823308.yXV3o4JbTB@thinkpad-pgpro>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox