Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oAzdU-0000yS-Ek for pgsql-hackers@arkaria.postgresql.org; Mon, 11 Jul 2022 20:04:04 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oAzdR-0002Xc-Ij for pgsql-hackers@arkaria.postgresql.org; Mon, 11 Jul 2022 20:04:01 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oAzdR-0002Wy-6R for pgsql-hackers@lists.postgresql.org; Mon, 11 Jul 2022 20:04:01 +0000 Received: from mail-pg1-x536.google.com ([2607:f8b0:4864:20::536]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1oAzdP-00010p-1Q for pgsql-hackers@lists.postgresql.org; Mon, 11 Jul 2022 20:04:00 +0000 Received: by mail-pg1-x536.google.com with SMTP id f11so4785718pgj.7 for ; Mon, 11 Jul 2022 13:03:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=j-davis-com.20210112.gappssmtp.com; s=20210112; h=message-id:subject:from:to:cc:date:in-reply-to:references :mime-version:content-transfer-encoding; bh=qIrjC0poHZSxF1MbzZevfDX64ZwagQrqjiKQyPxYOxE=; b=u4PrgtjFLKuOIsLu9j7AsRUlTjdce767y+dtFko/7D1UUL4J5F+vbPOx+29xPKb0pu CHuLk4dA9HAEY4gi3kdI1rfN3AC34VKkdoeXmIV4H8wvO7+1wKZbJOHNhNcsyWnoSBxL rsHsDMiuMRpJpVYTnunhFHU1c7MF9BeUk1PH+aLZ8kFQQVnWbIF2XDecRGAXwUmSzhPy shTWGvwXrI0uplZspm1Do0o0T1pmN9GO96vEuhLiZamCTqTJOrQqu5kAoSuCyDe8Zti4 aay6M8sczFHWLAssefmrdMo+mqks6qWJei/fgFgeJz0qlRhlLcpKkA8XKxcLdiOr70BQ GrTw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:subject:from:to:cc:date:in-reply-to :references:mime-version:content-transfer-encoding; bh=qIrjC0poHZSxF1MbzZevfDX64ZwagQrqjiKQyPxYOxE=; b=XJePojkMQZP2Y9bLYHU5darqvqQ/Y4DMoXDUPnFSoBlaATuobhbOH7m8JJbG+6NLu+ p3JoQ6skB8PDFli/gv7o7VI/pdlIicnm9PkuEjRWMO5AYqKer7LU63FYLK9uEoytSUWO 5Ujr7HLoh4XtMkNdOPoOTFM5CpA2/AYp7do3xp6y1HrW7gXaSQQ/+o6mXKl2BSA+LS9u Fw4pmk9m7BY5zvI/KKmbrG1nxc9xdl6wA6na/nLPg5t59UvBcFMOQK/ZFPMsoT5bT/oD 9DbmH41PDG7tn6QvZnMCm0HbDVWx+zapuFrIakndP9xKwXql4656p5AWIoOpT5wxBRt6 jpSQ== X-Gm-Message-State: AJIora8tniu7UFrVjZJMzp/N/pxmGhL4RVM27lNNwCc0NvW5gl27g2xn ZgdPFam+Ykp8RjPbfoYRke+yQg== X-Google-Smtp-Source: AGRyM1sX6PETFTlh+O3mSKQJae45FOqJn/n5beinZMwjamQnnST4lISQtruurdosLF1+/byQW128Qg== X-Received: by 2002:a63:1816:0:b0:3fc:c510:c839 with SMTP id y22-20020a631816000000b003fcc510c839mr17328423pgl.470.1657569836660; Mon, 11 Jul 2022 13:03:56 -0700 (PDT) Received: from jdavis.lan (c-73-231-146-4.hsd1.ca.comcast.net. [73.231.146.4]) by smtp.gmail.com with ESMTPSA id p123-20020a625b81000000b0052ab5740130sm5116063pfb.37.2022.07.11.13.03.55 (version=TLS1_2 cipher=ECDHE-ECDSA-CHACHA20-POLY1305 bits=256/256); Mon, 11 Jul 2022 13:03:56 -0700 (PDT) Message-ID: <72554626ddbb9ff1b8a218139fb2655d9fc5199a.camel@j-davis.com> Subject: Re: [PATCH] New [relation] option engine From: Jeff Davis To: Nikolay Shaplov , PostgreSQL Hackers Cc: Alvaro Herrera , Michael Paquier , Amit Langote Date: Mon, 11 Jul 2022 13:03:55 -0700 In-Reply-To: <3766675.7eaCOWfIcx@thinkpad-pgpro> References: <3766675.7eaCOWfIcx@thinkpad-pgpro> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5-0ubuntu0.18.04.2 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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