Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1shVP6-002rdm-7u for pgsql-general@arkaria.postgresql.org; Fri, 23 Aug 2024 14:36:40 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1shVP4-00ED0j-Ad for pgsql-general@arkaria.postgresql.org; Fri, 23 Aug 2024 14:36:38 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1shVP3-00ED0W-Um for pgsql-general@lists.postgresql.org; Fri, 23 Aug 2024 14:36:38 +0000 Received: from mail-oa1-x34.google.com ([2001:4860:4864:20::34]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1shVP1-0017zL-0d for pgsql-general@postgresql.org; Fri, 23 Aug 2024 14:36:37 +0000 Received: by mail-oa1-x34.google.com with SMTP id 586e51a60fabf-27032e6dbf2so1313509fac.1 for ; Fri, 23 Aug 2024 07:36:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1724423793; x=1725028593; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=xl0JmMZ+uuAa/K5IrCa/3hTny35VA7ghJ8xJt9ej9XU=; b=PaWqOSQoXjab9LUA+rKg3QNu37pk+dO3H061NJiFsFu1i845ayi36P7kQ6OSDcBagg lxqe1wekz3pJbQmn4IibzNC2elc8F9MTgle/gVPUKj0lNewWM971/51OGChDWdwrLMLt Qqw/LbhxdFkmoIGvAcnr3RAhJg7xwuoER8RqeB05Nj1dAXDskYKlMVJtYkeiDAOE1Vj6 TUWneG2jXM1hIXl4HPbVkzyU01MOVSrGNsSifT+EFueBvvIPGd163oW/I8CRe6K9v885 6g7HM1ZswepzJHg2ouKSrvwmQUnHvE04XUAiBEQ4pZssrSk2/gl8lE5DquuAtMpPVY1d IGng== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1724423793; x=1725028593; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=xl0JmMZ+uuAa/K5IrCa/3hTny35VA7ghJ8xJt9ej9XU=; b=d0Z/+BfN0wiQdEz7S3mKTUerF4a7OW8HOsOUet5v3C24t5iZ0uM5nCJN7kCZq18hYI IgJLN518g4sZxnwnFoW/K28NEUAWx1tkTQjaFjo/zkNbM63GD+MXNhFfEoODkeo47YeH vMGBIEeSby9yl9wzZc6A5uaonWDclz0jt8MNXoUmdq0q4t77n3UcTfXqfz2KNh58t/UN nhI4SogYG3a0UsOx/BSB59MrT1fd0EnA9Vh5xQV0nO+GRw5JP3kX2gv3ZRE2byQq5eD1 LfgwOXZnpLSTwAmvZAXq7F37tLRmpBkGHeSKjkbpbAjlzqStTxGEmuPcVFTunabAOta2 TfDQ== X-Gm-Message-State: AOJu0YzAebO8rDhfw5z0nAyiu4eh5h5UXhfXYwJgYCZ6CGvlP5xGuj40 3XC/pXKUL/z0dpzlq2BV16fd02y83pR0RrQILYcf7NLUVyqkF/htW8a+ato/5EYgyfKuTUm/m+q R5ojAcvAxq9WZ7mHuJvFXPlYyDZMOaA== X-Google-Smtp-Source: AGHT+IGgeNnmQK5U4FK0LHnE4N/eVzF6CNB/aso0HRJ1A9oW7fhOJOiOHHcRJ5rnJmKXi7WvrnViyn+/67bbd/sMthU= X-Received: by 2002:a05:6871:5826:b0:25e:7a9:b603 with SMTP id 586e51a60fabf-273e646613fmr2754174fac.5.1724423793160; Fri, 23 Aug 2024 07:36:33 -0700 (PDT) MIME-Version: 1.0 References: <2087380.1724366535@sss.pgh.pa.us> In-Reply-To: <2087380.1724366535@sss.pgh.pa.us> From: Morris de Oryx Date: Fri, 23 Aug 2024 09:36:21 -0500 Message-ID: Subject: Re: Is there a way to translate pg_amop.amopstrategy into a description? To: Tom Lane Cc: pgsql-general Content-Type: multipart/alternative; boundary="000000000000a23add06205ab336" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000a23add06205ab336 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thanks for the confirmation. And, I'd say that this feature would go under "nice to have" rather than anything more important. Although, it *would *be nice. On Thu, Aug 22, 2024 at 5:42=E2=80=AFPM Tom Lane wrote: > Morris de Oryx writes: > > What I'm hoping for is a function like > > get_opt_class_strategy_description(optclass, straregy_number) I've > > looked at the source a bit, and it seems that there is no such > > function, and that it might well be difficult to implement. The > > strategy numbers are, as far as I can see, local to the specific > > opt_class, which has no requirement to label them in any particular > > way. > > That's correct. For btree and hash, the meanings of the strategy > numbers are determined by the index AM; but for (IIRC) all of our > other index AMs they're determined by the individual opclass. So > anything like this would have to be implemented by dedicated code > in each opclass. Perhaps that's worth doing, but it'd be a fair > amount of work. > > regards, tom lane > --000000000000a23add06205ab336 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks for the confirmation. And, I'd say that this fe= ature would go under "nice to have" rather than anything=C2=A0mor= e important. Although, it would be nice.

--000000000000a23add06205ab336--