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 1tU7mD-00EJRq-Jz for pgsql-performance@arkaria.postgresql.org; Sat, 04 Jan 2025 17:17:30 +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 1tU7lE-00BwW5-9w for pgsql-performance@arkaria.postgresql.org; Sat, 04 Jan 2025 17:16:27 +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 1tU7lD-00BwVx-SG for pgsql-performance@lists.postgresql.org; Sat, 04 Jan 2025 17:16:27 +0000 Received: from mail-ed1-x52c.google.com ([2a00:1450:4864:20::52c]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tU7lB-000Db9-2b for pgsql-performance@lists.postgresql.org; Sat, 04 Jan 2025 17:16:26 +0000 Received: by mail-ed1-x52c.google.com with SMTP id 4fb4d7f45d1cf-5d3e6274015so23201704a12.0 for ; Sat, 04 Jan 2025 09:16:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jp-hosting.net; s=google; t=1736010982; x=1736615782; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=gYVdGg2OHqFeBFXWecpfU94ST80Ih6kxjmfjJMcnlTU=; b=TCZLLBbbomU3CtO/5mT1GpzNto3GBMaqg6ygLKVVUXD6PIyeZR3t8dbn/wSC53r8GF FbUqumOCNvM5gcPIDnOxPaczW8733Xjhl0I1zIbzl/E40do83sn+xFoVe9p3oLyJweLp 0945aFJiTY4GI3RllCo655WUOERYdVzttCg/qHpOTfdaVcFyCkdev7h5Oilw1baSHvtS Chwl4nD1E/2F4uI/I7N8Ky07LWsMgVLVhKRkEmeFTKd/DjWquoj3VY7jwS0CGjqAQXvj 72t05Zm+GSq6pYRG/wELr8FxgOT9OzOtY4qbOR5M6MPSamwVf30CxxkYaFjv62gML1X9 AoJg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1736010982; x=1736615782; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=gYVdGg2OHqFeBFXWecpfU94ST80Ih6kxjmfjJMcnlTU=; b=qHfxXBDAfnu5LmFM010HnICXTpSPX6qPOvKyxwz6RCyT1WF0Plu+1Zi/wrGFnTwaZt IRmaxIaQvfXPjQEjRcSrx7EgzVODpfn5U22eo8VXp5BbzaoGudT1LsN7m2b9/2yWzHhA ysU5LVP6TvOtioFu+Hndsx/QFTN53Eu2d6KoTGmyNESl02SVVXJEV7PIlrguC06Xilum RJfZO7BFaeTPspOfJ4nYp6jyMK6DPOClpZE3xO4iEMsYz/IvLRdq5cZwP+/Ewp4RMNch wtZcoI1ZyjMf8ElFcNTzkyUvl3si0czUppz6EI4hp1NXnhyyc7E7cynVFnbLsnNaHFrg /n+Q== X-Gm-Message-State: AOJu0Yxt/hxmAkTQNWpfxfNXQWl5oC5Z3g2ALR+tKkwiDpQgQ9ksAaos iXr/CvXEWWbxUsfgH8u2qmJ8Ja/aObKRK2tWE/9GKjYiTO53nZOoEg9HM9z78Q+6KXoKEUKlWDQ 35dPs+THQBQwlVvnDgq++aIUnFdtt067Ugcf3zTfQJ+w6jPPlwA== X-Gm-Gg: ASbGnctliuwpYp9Cja/D/qXfAq/yA45x695ww7ewj3wXD9VcWmghqx/TiDFKbdoWrsb 6cNX/OtgdjpklbRY66rlV7X+wGNNXAqVY5J5tyg== X-Google-Smtp-Source: AGHT+IGaCPlLfLlKBkI8xxdjyOaPuRkVYY3we2nEAKpQhRbBNUnzBIOyBpyTOb3hOpldX7c9tB12K9b6etiXGSg3Veo= X-Received: by 2002:a05:6402:3221:b0:5d0:bcdd:ff97 with SMTP id 4fb4d7f45d1cf-5d81dd83edemr44577090a12.5.1736010981571; Sat, 04 Jan 2025 09:16:21 -0800 (PST) MIME-Version: 1.0 From: James Addison Date: Sat, 4 Jan 2025 17:16:06 +0000 Message-ID: Subject: Question: consolidating strpos searches? To: pgsql-performance@lists.postgresql.org Content-Type: multipart/mixed; boundary="000000000000e24cbc062ae48da6" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000e24cbc062ae48da6 Content-Type: text/plain; charset="UTF-8" Hello and Happy New Year, I'd like to validate or reject a performance-related PostgreSQL patch idea, regarding multiple strpos calls that operate on a common text input.