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 1v8zGt-008BML-5p for pgsql-www@arkaria.postgresql.org; Wed, 15 Oct 2025 11:02:18 +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 1v8zGr-005un1-19 for pgsql-www@arkaria.postgresql.org; Wed, 15 Oct 2025 11:02:16 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1v8zGq-005umt-RO for pgsql-www@lists.postgresql.org; Wed, 15 Oct 2025 11:02:15 +0000 Received: from mail-lf1-x131.google.com ([2a00:1450:4864:20::131]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1v8zFT-001syZ-2l for pgsql-www@lists.postgresql.org; Wed, 15 Oct 2025 11:02:14 +0000 Received: by mail-lf1-x131.google.com with SMTP id 2adb3069b0e04-57bd482dfd2so6419651e87.2 for ; Wed, 15 Oct 2025 04:00:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1760526050; x=1761130850; darn=lists.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=HdbjmgMBjJHYi6wgJZnl8/CXa2dV/QnwUPxut76HXUo=; b=IRPVcsZHVwcBIwI5KajL4IMrjChewfPawdhu2njZAT3gncIpWClO6v09ZKDRqUzVYu +cr4ZnJqk4/uWM/Zc3D6N423cMuivn1CgcFMbbjLtfab0SVHLF08f4B94JHN4TaaLPLM dX6FQoNX7t/YaVBUcG/0CNGXQxlmB2jOGmGOCyR/vJ8/a/gZ8B6UvKRfwxlLNVIda3rn FZcqNuthnegBy9IG8O1h+luSC5BUU/J+lmf/CSjLmGXla3Ofg9bH8teFMJIIDVB2v7XB qXOahqrp9/OMYAq27Vbf7I5Z27HSOBB7q4YO0KkuklRsqVqFTitv7BGS66gS0DypWp9B o/IQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1760526050; x=1761130850; 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=HdbjmgMBjJHYi6wgJZnl8/CXa2dV/QnwUPxut76HXUo=; b=ZPq5n4pFPGM2YmuVNGJl1mR+q1sG5B8ho6nyKqRnVogtmbsMU7mehPj+4btFse7ncI gxRBUScwZIBYnz1ox7cXOa0Ye5l8qDm8N2pAPn+2flZlQ+LuU36xdbxSbCAvjV7gUeZ0 anxoOvuuGlo/FFHcV64pEXykBiA0ROfsp/AM+OGj4xCHPrnsR5/f5FEZzx5dDYXh7qNb 3HcaLZE7Iti0wTKJTBPIhDYFXoIOVa4glTIVT+QHqy8rHRTdIu1g3WhzM2n5VLDylDPG uurb7meH52S65ex5030+WGhNVBMSnu8FIuruFU3Pw2wEUq3vMW+1/3Z0LBq4S93BnRef Ubxw== X-Gm-Message-State: AOJu0YyHGWbFUXHHzeWR7X4jYE6ET+EKZs72ss8C1Sh4tR+PV8wfW0Ig PObQQ4Ya5NRRCtNv0ksT1pTnRREtPTn50Z+BaX8rocodNuUd3vz2Eo9cg53mWOEmg6JNIUnUpgT 458dCwwOBsdfdDEbsl24gWWjo/bfSrT9ALoAAXU0= X-Gm-Gg: ASbGncvt49mvhNNyQYHUQZhrkmV24brjNzOdx69kis7QRn10xHifOzwBLCWziKc4uRc oRAyUOjcY8pMgIKug2STvwFsPvh2ybQQyvCVTaQtDo+Kziasr+CPBO8DM8yuG8kQpa2uHvVPEhj 5owHe6QVM2tUwzvQxsEuYprR3sicq1z0B7kZYqsqEEHnL6KNW/Auj95OnwKmy6s0ZZpGRAjJ19o OJI75Lx/wFK2w2mQIjhbu1ToUagVfxQRWTPby9s9aMDwzr/y5xn4n/eD/MSWnNTXPdt9VPgV2XH IPibdaqb5CCMQgSQ X-Google-Smtp-Source: AGHT+IHN4V4dVJlu0zazCAxwSHXd7KR3D+aNQx2SKbAHz1qHs3A4f89DbLeTMYxEIa4SHpnYON8YFGfgcaOXY+66FsY= X-Received: by 2002:a2e:bcc7:0:b0:372:950f:2aff with SMTP id 38308e7fff4ca-37609e0ed4emr79279681fa.27.1760526049784; Wed, 15 Oct 2025 04:00:49 -0700 (PDT) MIME-Version: 1.0 References: <0781CAB9-187C-42C6-BB66-F82F66591F92@yesql.se> In-Reply-To: <0781CAB9-187C-42C6-BB66-F82F66591F92@yesql.se> From: David Rowley Date: Thu, 16 Oct 2025 00:00:38 +1300 X-Gm-Features: AS18NWAn2z3dN3HuCjZNqqyhpB-o4EhK5RHXBV7pwqGCukOR_gdKNSd34b6o0yk Message-ID: Subject: Re: Typos in the featurematrix To: Daniel Gustafsson Cc: pgsql-www@lists.postgresql.org Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue, 14 Oct 2025 at 20:46, Daniel Gustafsson wrote: > While working on something else I noticed that the featurematrix has a few > typos, unless there are objections I'll go ahead with the attached. Patch looks good. I had a read and found a few more: conjunction with a RETURNING clause to to pass data up to the containing query. too many to's. description: Extend statistics can help the query planner provided better plans I think "Extended" and "provide" instead of 'provided' or better yet "generate" for queries that have "OR".clauses as well as "IN/ANY" lookups over lists. For I think "OR" should be followed by a space instead of a fullstop/period. JSON data strings can now to be converted into records and new functions to "to" seems misplaced. description: "Write conflicts that occur during ogical replication are\ "logical" available in order for a standbys of the new primary to correctly switch to "standbys" should be singular or the "a " should be removed. description: Ability to require synch messages from multiple prioritized standbys I don't know that "synch" is necessarily incorrect, but I don't see it being used in our codebase. We normally spell it "sync". description: adds support for authentictaing against a RADIUS server "authenticating" description: replaces user and group concept by a more generalizes role based Maybe "replaces user and group concept with a more generalized role based" description: simply way to return the result of an arbitrary query in pl/pgsql "simple" David